I would create a single project containing all the different locale specific stuff and maintain that single project. Then when you deploy to the Market, just create a script that changes the package names so you can upload them to the Market as seperate apps. That's what I did when I was maintaining the paid vs. free versions of my app. The free version was automatically generated from the paid version.
On Jun 3, 4:43 am, Thx Ftw <thx...@gmail.com> wrote: > I'm currently creating an application that is both language localized, but > also country specific. 95% of the data in the code is going to be similar. > I'm very well aware that I can use the strings file for language localized > issues, but the application should also be able to install side by side. > > So you could have a UK version of the app, as well as a USA, FR, BE, NL > version of the app. The app can also have different names for the different > countries. > > I would love to hear some opinions of people who have already done this sort > of stuff. My project is currently in a git library, but i would like to stay > away from branching as much as possible. Although i do feel that branching > the android manifest is going to be my only solution for that problem. > > Things that are localized per country: > - some colors and graphics > - some settings details not visible to a user > > Anyone have any expert insights on this? Perhaps using conditionals or > resources? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
