[android-developers] Re: Advice on Beta Release

Vote for issue 4319
"Market should allow Beta releases"
http://code.google.com/p/android/issues/detail?id=4319

Snippet;

"
Add 1 field to submission process for the release level (beta /
public)

The market should, by default hide all apps marked Beta.

Users may optionally choose to view said Beta apps (settings)

They can have their own section, or just get thrown in with the rest,
but
special formatting applied (eg red title, or special beta icon)

"

On Oct 22, 11:22 am, Smelly Eddie <ollit...@gmail.com> wrote:
> I think i will stick with Andrei's advice and release it into android
> market.  I dont think we need to support dozens of separate locations
> to provide access to apps when there is already centralized source.
>
> I will however encourage/submit a ticket for the android market to
> allow apps to be markedBEta, and allow users to choose whether4 or
> not they seebetaapps.
>
> On Oct 16, 4:44 am, André <andre.rab...@googlemail.com> wrote:
>
> > I have implemented the Flurry API (see flurry.com) into my own game
> > Puzzle Blox Arcade! and released it asBetaon both AndAppStore.com
> > and SlideMe.org. On both websites I have marked it asBETArelease in
> > the summary/description.
>
> > Flurry enables you to get detailed statistics about the users of your
> > app, the devices used including screen resolution and firmware
> > version, etc. Everything anonymously of course but very helpful to
> > find out who your customers are. The most important feature though is
> > to report errors and unhandled exceptions. This helps you to find a
> > lot of bugs and issues!
>
> > If you don't like Flurry and the statistics it generates you might
> > want to implement such an error reporting feature yourself of course.
> > And make sure the user can disable the statistics as not everybody
> > likes to be such transparent obviously.
>
> > Both AndAppStore.com and SlideMe.org are very good start to publish
> > your apps. Depending on the type of application you will get a few
> > dozen daily downloads.  In the meantime I have several hundreds of
> > installs which provides my with a very good overview of the average
> > fail rate. Once the rate of failure goes down to an acceptable level I
> > will release it to the Google Android Market finally.
>
> > -- Andréhttp://android.rabold.org
>
> > On 15 Okt., 21:57, Smelly Eddie <ollit...@gmail.com> wrote:
>
> > > SO i have an application that is doing pretty well on my dev. device,
> > > and it is almost ready for prime time.
>
> > > Trouble is I am only one man, so I would like to release the
> > > application under abetarelease to work out any prominent bugs with a
> > > more strenuous workout.
>
> > > So I was thinking;
>
> > > * Just release the app through the Market and note in the description
> > > and title that the app is inbetamode, and to use at own risk
>
> > > * Round up a group of friendly strangers with android devices and
> > > share a signed (short lifespan) package directly with them.
>
> > > * push and pray - just release the app and hope the community will
> > > overlook a few undocumented features (I would like to avoid this!)
>
> > > Has anyone else taken a phased approach to releases? Any advice for a
> > > first time publisher?
>
> > > P.S. - My app will be free, and likely released as open source of
> > > flavor, so I am not worried about losing profits.
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---