Flexibility and future proof app development

aeric

Expert
Licensed User
Longtime User
I am currently working on some projects. I think I am wasting my time making one legacy app so that it will be easy for existing users to upgrade to new version. The app is a free app with ads. I am building a Pro version to allow existing user to login back to their accounts and migrate/upgrade to the new account. It took more time I expected.

Then I am also developing another new app from scratch and I have considered too much about adding more flexibility so that it would be easier to add new features in the future.

My younger brother scolded me and asked me to come out the app with very basic features but I thought if the app is too simple and lack of features then it has less selling point to compete with existing apps.
 

LucaMs

Expert
Licensed User
Longtime User
aeric said:
My younger brother scolded me and asked me to come out the app with very basic features but I thought if the app is too simple and lack of features then it has less selling point to compete with existing apps.
Click to expand...
Younger brothers are always wrong ?


To me too someone suggested that I immediately publish an app that I developed a long time ago but, as for your same reason, I didn't. It, with few features, could be commented in a derogatory way and any subsequent additions would not make it regain a good reputation, I think.
 
Last edited:

andymc

Well-Known Member
Licensed User
Longtime User
You're brother might have a point. Too many apps leave it too long to come out as the developer keeps trying to add features. One good approach is to release a version with the basic features in place (a minimum viable product), then release regular (weekly) updates adding a feature in each update. Regular updates keep users interested and you can request feedback before adding more features.
 

Sandman

Expert
Licensed User
Longtime User
I agree with andymc, and just wanted to add that this is a known concept called YAGNI, for You Aren't Gonna Need It.

You aren't gonna need it - Wikipedia

en.m.wikipedia.org

However, if we're fair, there is such a thing as too few features. You would probably find it difficult to launch an email client that could only recieve mail and not send, for instance. So it might take some work trying to figure out the correct level of "this is enough".
 
Last edited:

f0raster0

Well-Known Member
Licensed User
Longtime User
aeric said:
very basic features but I thought if the app is too simple and lack of features then it has less selling point to compete with existing apps.
Click to expand...
We discussed it before when we were speaking about the POS - Better go for a simple App or it will be never finished
 

AnandGupta

Expert
Licensed User
Longtime User
f0raster0 said:
Better go for a simple App or it will be never finished
Click to expand...
This always happening to me.
I am full time Xbase++ and .Net developer (office projects) and get little time to make Android app. That too many of my apps are half baked so I do not get chance to submit any. I have to stop at basic features only and then only I may be able to put some app in GPlay.
 

MichalK73

Well-Known Member
Licensed User
Longtime User
I read and read and I see that I am making the same mistakes. I have 4 unfinished own projects and I am still waiting for free time to polish them to be nice, new functions instead of being available for use. I can see I have to change my approach to this.
 
You must log in or register to reply here.
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…