IPhone : Best practice for managing multiple app versions on iOS

on Tuesday, March 31, 2015

I've read some topics here with similar questions, but most of them are related to managing FREE and PAID version of the same app. I have a slightly different situation. I'm about to develop a series of apps (3+) that have a very similar design, mostly the same scenes and differ in colors, labels, images, web requests with minor differences in data model and scenarios inside the app.


The idea is to make a "prototype" app which I can reuse over and over to make each new app faster. Maintaining these apps is also a big concern.


Many topics suggest to use multiple targets in the same app and preprocessor macros. I'm not sure about that, because differences in the future apps may be much more significant, which will make conditional code a huge mess. Especially with 5 or 6 different apps.


Making separate apps and just copying files that a similar is always an option, but doesn't seem reliable when it comes to maintaining.


To summarise: There will be like 3 or 4 apps with very similar design and flow, but still will have lots of different code and behaviours. I would like to easily make changes to a specific app (add a storyboard scene or a couple of classes) but I would love it to not become a maintenance hell when it will come to changing something that applies to all the apps the same.


Is there a "best practice" way to achieve that?


Q: Does it have to be multiple apps? Have you considered localizing or in-app purchases?


A: Yes, it does. These apps have nothing to do with localization. Think of them as shop apps for completely different stores, but sharing the same design language.


0 comments:

Post a Comment