Hi Matija, maybe we should join forces. I didn't know you are implementing something similar. Below is my post for feedback: http://groups.google.com/group/android-developers/browse_thread/thread/fe1d5a62f863c69f#
Currently, the OI Update provides both, an activity for checking and a service for immediate version information. Have you had a look at VeeCheck about the xml file. AndAppStore.com supports it. So I wouldn't invent a new one. Cheers, Friedger On 30 Okt., 19:53, Matija Grabnar <[EMAIL PROTECTED]> wrote: > Shane Isbell wrote: > > Hi Peli, > > > If you guys at OpenIntents could do an intent for checking upgrades on > > the Android Market, we could put an option at SlideME to allow > > developers to configure the versionCode and application UUID, for > > querying of version upgrades. It may make life a little easier for > > some developers who cross stock applications. Would anyone else be > > interested in this feature? > > There is already an intent registered for that > athttp://www.openintents.org/en/node/128#comment-form > I'm working on something similar. I note that the intent on openintents > only immediately returns the version. This is still quite useful because > by using this interface, applications that would only need the internet > for checking for new version can skip declaring INTERNET in their manifest. > > My idea is slightly more elaborate: an application which takes an intent > with a URL, and an application name (call it registering for updates, > something any apps would only need to do when they are run for the first > time). > > The update app would keep a list of all apps and their URLs and check > the URLs periodically to see which apps have updates available, and > display them as notifications for the user. In addition, the user would > be able to select "check now" for any of the registered apps, or to > disable the checking for new versions (this comes in useful when you > KNOW there is an update, but the update has bugs or a new GUI or some > other reason why you don't want to download it - and you don't want the > unwanted update cluttering the reminders). > > A further idea is that the URL should point to an XML file that would > look something like this: > > <update application="SomeNiceApp" version="7" visible-version="1.3beta"> > <changelog version="6" visible-version="1.3alpha"> > Fixed disconnected chameleons bug in 1.2 > The flurgle button can now frobnitz. > </changelog> > <changelog version="5" visible-version="1.2"> > Description of changes between version 5 and 4. > </changelog> > ... etc ... > </update> > > That way, the user could get a full changelog between the version they > have installed and > the most current version, even if they had skipped some versions. > > Would people here be interested in having such an intent installed on > their phone? Would they configure their applications to use it? Or have > I gone off in the wrong direction? > > I'd be interested in your feedback... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
