Re: [iphonesb] Different App Bundles for Release VS Beta?

My app, FatWatch, is a weight tracker that holds a lot of data locally, so it's easier on a tester if the beta doesn't require them to back up the release version and put their real data at risk. A beta that acts as a separate app is useful.

On the other hand, if your app only requires a name/password to fetch everything from a server, then the app is "disposable" and there's really no need to make a separate bundle ID for the betas.

If you are going to use a beta bundle ID, you should also change the app name and/or badge the icon, to reduce confusion. (Splash screen is OK but then you have to launch them to tell them apart.) This is no harder to do than changing the ID, since they are all keys in Info.plist.

On May 3, 2011, at 7:08 AM, Stephen <stephen@officetime.net> wrote:

> Is it better practice to have a different bundle ID (hence a separate
> app) for your beta ad-hoc distribution VS your release version?
>
> This would mean if a current beta is bugged users could go back to
> your release app just be opening the other app. However it's more
> work to maintain both and potentially confusing to your testers to
> have 2 copies of the app on their iPhone.
>
> Thoughts?
>
> --
> You received this message because you are subscribed to the Google Groups "iPhone Software Business" group.
> To post to this group, send email to iphonesb@googlegroups.com.
> To unsubscribe from this group, send email to iphonesb+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/iphonesb?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "iPhone Software Business" group.
To post to this group, send email to iphonesb@googlegroups.com.
To unsubscribe from this group, send email to iphonesb+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/iphonesb?hl=en.