We are launching a new application for international market. There would be slight changes based on the country in terms of the dynamic content from web-services. We are confused whether we should go with application for all countries which will be customized based on user country selection or multiple apps with respect to countries.
I would really appreciate an intellectual and best help from the expert.
I'd suggest centralized solution, with different access levels/features based on countries - then later when you'll grow you can do load balancing for CRUD operations, not based on country.
Follow and read this link: http://www.information-age.com/5-tips-successfully-launching-mobile-app-international-market-123460818/
Depending on the content of the application, it always a good a idea to have central application and the users can then just select what country content they would like information on.
Creating multiple applications to handle language and cultural variations would result in a maintenance nightmare. Your application future would have a very short horizon as success will demand more applications which require more maintenance which eats up your developer time leaving nothing for new features. The calculus is simple. All credible development environments will provide language independence and the ability to control page navigation based on a language key that you can read from your users web or device profile.
On the other hand, if you are considering a mobile application I would avoid a generic mobile development environment unless you plan to go beyond the 98% of the market held by Apple and Android. In discussing this with vendors of such systems, they universally have agreed that unless you are looking to support a range of platforms beyond just Apple and Android you'd be better of writing two applications. The generic systems were conceived to write applications to support Apple, Android, Blackberry, Windows Phone, Windows Universal, etc. The problem is that there are only two vendors left standing after the phone wars. The overhead of working in a generic solution saturated with "if apple then do this" and "if android then to this" will add about 50% to your code and still curtail your ability to take full advantage of the device. This is a reasonable compromise if you are supporting 5 targets, but not for just 2.
You might want to consider coding your application in either Android or Apple depending on your target market and then outsourcing the other. Outsourcing can have challenges, but this represents the simplest case. Given the Android/Apple code create the Apple/Android code to do the identical thing taking advantage of best practices for the second device. The core logic will be the same and it will be easy to QA.
- Badges
- Science topic
- Similar topics
- Computer Communications (Networks)
- Simulators