Here I have collected a rake that can be stepped on when developing an application. We filmed several projects with this rake, but I suspect there are more. If you know, complete it.
Marketers who have sold their souls to the devil for monthly KPIs and almond cappuccino can convince you for as long as they want that building a mobile app is fast, cheap, easy and effortless. But we will be honest and admit right away - creating a full-fledged application taking into account the peculiarities of a business will not be simple and easy, it cannot be cheap and fast, and if you believe in miracles and in general everything that is written on the Internet, it can also be sad and painful ...
Big beautiful fashion applique that magnetically attracts new customers and does not let go of old ones, addictive like heroin and fast like a Ferrari, useful, cool and efficient like Asian schoolchildren - this is always a lot, a lot of work. Work, it is only at school is equal to the strength multiplied by the distance traveled. In business, it is always money multiplied by time.
On the one hand, everyone seems to understand this. On the other hand, budgets are not rubber either, well. Therefore, on the face of any manager of any link, at the sight of an estimate, it is always read "where to save money here, eh?" And often the result of these reflections is the most fig decisions that ultimately lead the whole project to a dead end, the people involved - to depression and abuse on Fridays, the budget - to bloat due to urgent patching of holes, and management - to citing Russian classics about “ you wouldn’t be chasing cheapness ”.
Let us outline in a few words how this happens.
1. Let's submit the project to LLC "Horns and Hooves"!
Choosing a contractor based only on pricing policy is a vicious practice, no matter what you do: are you looking for IT specialists or mandarins on the market.
, , , . , , , .
, , , . – . - – , .
. , , . – .
, , , , . , .
2. , , , !
, «» , , , .
– . , – . , , – . , - – .
, , .
3. , !
, . , . . « ». , .
. . -. - , - . , Exchange, , , , .
: «, -, -, !».
, , . – .
, . . . , , , , , , , , . - – , . .
, , , , , -. , , , . , , , – , – .
, .
, – , - – , , -, , . – , . , , . , -, ? - ? , ? , ? , , ? , ... ? - .
4. ?
, .
- , , – . – .
, . , – . , , «» . . , , . , - – . .
, , , . . . ( , , ). 5% ?
5. ?
!
, , , . , , , , . , , , .
. , , .
, , , , . . , , – , , , .
Guys, we need to test. At least minimal, at least not very deep. If you're running out of budgets, leave plenty of time for the testing phase. Believe me, the lack of normal system testing will later result in such money that you will curse the day when you were advised to give up in the style of "and so it will do."
Sorry if it hurts now, but in the next article, I promise, there will be pain relievers in the form of four reasonable savings options. Both sensible and painless.