I do this kind of incremental update for the PayPal version of my
app.  I do it in the same way that Brad described.  If the app finds a
new version on the server, it pops a dialog asking the user to update
or postpone it.  If they click update, it downloads via an AsyncTask,
and installs via the following code:

Intent intent = new Intent();
                                Uri uri = Uri.fromFile(file);
                                
intent.setAction(android.content.Intent.ACTION_VIEW);
                                intent.setDataAndType(Uri.parse(uri.toString()),
                                "application/vnd.android.package-archive");
                                startActivity(intent);

You could then delete the downloaded apk file on the next run to clean
up.

On Sep 22, 7:00 pm, Chris Stratton <[email protected]> wrote:
> Actually the att restriction is a relative non issue now that someone
> wrapped the adb install capability (which always worked) into an end
> user sideloading gui.  That basically makes installing random third
> party apps as easy as installing approved apps on att's "other" touch
> screen phone family - in both cases you have to use a piece of desktop
> software to do it.
>
>
>
>
>
>
>
> Jason wrote:
> > If you're talking about this:
>
> >http://www.mobilecrunch.com/2010/06/15/lesson-not-learned-att-locks-d...
>
> > (or similar) then there is pretty much nothing you can do short of
> > actually publishing the app to the app Market.
>
> > Of course there's nothing wrong with this, you could just put some
> > sort of password on the app so if anyone else downloaded it they
> > couldn't use it.
>
> > I think there may also be some options regarding who can see the app
> > on the market that may be useful, but I haven't actually published yet
> > myself so not sure.
>
> > Maybe someone with more knowledge of the Market could help
>
> > On Sep 18, 12:20 pm, Yepher <[email protected]> wrote:
> > > I am developing an Android application for a customer. I want to be
> > > able to provide them (no one else) incremental updates but I am not
> > > clear what the procedure should be.
>
> > > I don't want them to have to install development tools or root their
> > > phone. These are non technical folks who would have no idea how to
> > > accomplish root a phone or use a command line interface.
>
> > > When I develop iPhone applications for them this was easy. They just
> > > give me the device UDID and I send them a binary that can be drag and
> > > dropped into iTunes.
>
> > > How is this done on Android. I have tried loading the application from
> > > a web server but the devices says it is not allowed to be loaded
> > > because of security reasons. In setting->Applications there is no menu
> > > option to "Allow Unknown sources".
>
> > > Thank  your for any help you can provide on this matter.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to