Sep 28 2014, 08:05 PM
QUOTE(mobileoop @ Sep 28 2014, 01:07 PM)
The question is quite subjective as it depends on how good is the developer and also the complete requirements from the client. If it is just a prototype app that gets data from server and displays on the app, it can be developed within a week time.
I have received a few requests to build a "simple" XXX app. After I try to get more requirements from them on what do they expect to see on each of the pages of the app, that's when you will understand the complexity of the app. Usually, they will have many tiny requests like: When I tap on this button, it should animate the whole screen and etc... I should be able to swipe the top of this screen and the the next screen will be ....
Phew.. I actually have to spend a lot more time on those tiny requests rather than the main function itself. Some of those tiny requests can not be developed easily due to some technical challenges. The clients do not understand the technical challenges and thought those requests can be implemented easily.
The funny thing is I actually received a request to build an app like HungryGoWhere. I told him honestly that HungryGoWhere can not be built easily and it has been build since 2006. It is almost impossible to replicate exactly like HungryGoWhere with limited time and limited budget. I told him that if he wants me to develop the app for him, he has to give me the complete requirements or divide the requirements into a few phrases. I can help him to develop from another phrase to the next. Without those requirements or a clear scope, I am not going to take the projects as the scope of the project can be limitless.
If you ask an app developer to build HungryGoWhere app for you (without a complete requirements/clear scope) is almost like asking a web developer to build a Facebook for you.
Got also request like that.i said phpfox.you dont have money.Yes sometimes customer keep delaying by asking detailing non functional requirement instead of real businese flow objective.Sometimes hard for me to argue tiny part like this.Tiny seem but it can uber complex or changed the whole system flow.I have received a few requests to build a "simple" XXX app. After I try to get more requirements from them on what do they expect to see on each of the pages of the app, that's when you will understand the complexity of the app. Usually, they will have many tiny requests like: When I tap on this button, it should animate the whole screen and etc... I should be able to swipe the top of this screen and the the next screen will be ....
Phew.. I actually have to spend a lot more time on those tiny requests rather than the main function itself. Some of those tiny requests can not be developed easily due to some technical challenges. The clients do not understand the technical challenges and thought those requests can be implemented easily.
The funny thing is I actually received a request to build an app like HungryGoWhere. I told him honestly that HungryGoWhere can not be built easily and it has been build since 2006. It is almost impossible to replicate exactly like HungryGoWhere with limited time and limited budget. I told him that if he wants me to develop the app for him, he has to give me the complete requirements or divide the requirements into a few phrases. I can help him to develop from another phrase to the next. Without those requirements or a clear scope, I am not going to take the projects as the scope of the project can be limitless.
If you ask an app developer to build HungryGoWhere app for you (without a complete requirements/clear scope) is almost like asking a web developer to build a Facebook for you.
Quote
0.0147sec
0.29
6 queries
GZIP Disabled