All About Symbian - Symbian, Nokia and S60 unwrapped.
Application auto-update the way to go - as part of a two-pronged strategy?
Published by Steve Litchfield at 7:13 UTC, August 30th 2010
Applications are rarely completely static. Anything with a decent amount of functionality is bound to have either flaws - which then hopefully get fixed - or planned improvements. The big question is how to best to get these new versions out to users. In this news editorial, I look at how application updates work for the three big smartphone platforms of the moment, Symbian, iPhone and Android. What can those in the Symbian world learn or implement?
On-device app stores started with Nokia's Download! system, circa 2006, of course. The experience was very bare bones and the number of apps was artificially limited by Nokia, for good or bad. The end result was that it was useful but not world-shattering. What was needed was something far more open.
Enter Apple and its iPhone App Store in 2008. The combination of powerful hardware which invited ambitious titles (especially games), a relatively easy route to development and, most of all, an on-device store which almost anyone could get into (subject to approval, i.e. conformity with Apples Terms and Conditions). The result was an overnight success and two years later we have 100,000+ applications listed. Yes, 95,000 of these are trivial novelties, but the download numbers are still mightily impressive.
So what happens in this world when an application gets updated by its developer? The on-device App Store client notices that an installed app has an update and marks the App Store icon with a little numeric flag (to indicate how many apps need updating). It's then up to the user to want to start up the App Store client and then either tap on applications to update them manually or accept a batch of updates with 'Update all'.
To be honest, this is fairly painless, but it does require some user interaction - I picked up my daughter's iPod Touch just now and the App Store client was showing no less than 34 apps needing updating! Clearly this aspect of computing was something she didn't pay any heed to - and I suspect she's not alone.
Under Android things are (on the whole) worse at the moment, in that a manual trip into the Market (depending on device, you may also get notified via the top notifications bar) will show you, under 'Downloads', what's waiting to be updated, but you have to tap on each explicitly and, worse, acknowledge two extra dialogs - per application. Under the upcoming Android 2.2, there's apparently an 'Update all' option, as with the iPhone, though developers will need to embrace this for their apps to be included.
And so to Symbian, the world marketshare leader for smartphones by a country mile but rarely perceived as such by the media. Nokia, by far the biggest partner of Symbian, has its Ovi Store, a serviceable app store that followed the iPhone's lead but which is evolving at, some would say, glacial pace - not helped by being implemented as a glorified Web runtime widget, i.e. a dynamic web page. There's no concept whatsoever of application versions on the store and no official way to notify users who have already downloaded something. Apparently it's 'on the roadmap' - though with Nokia World 2010 just around the corner, it's possible things might change next month.
Sony Ericsson's current Symbian phones rely on an even clunkier Web-based system, involving multiple instances of Web that just eat up the OS and with no apparent advantages.
At first glance then, the iPhone seems a slam dunk for first place, followed by Android and with Nokia in a distant third, in terms of application updating. However, I contend that all this isn't necessarily the only - or indeed right -way to update applications in the first place.
Moreoever, it could even be argued (you may want to lie down for this contentious opinion) that Symbian is even vying for the lead in terms of smartphone app updates - not because of manufacturer app stores - the places where a user discovers apps in the first place - but in spite of them.
You see, with no auto-update notification system in place from the OS itself, or from an app store, applications have to check themselves for an update, direct from the developer's servers. This has two huge advantages:
- the user doesn't have to lift a finger. When an app is started (or on a regular schedule), it goes online and checks for an update automatically, in the background, prompting the user to press 'Yes' to download and install an update if appropriate.
- updates obtained from the developer's server will be bang up to date and not a month or too old (as is usual after passing through some approval process). In the case of the famous Gravity social network client, you even get access to alpha and beta versions this way - very cutting edge.
All of which sounds wonderful and yes, if every Symbian application (and game) did this, then it would be blatantly obvious that this is the best way to go. The only slight fly in the ointment is that not many developers seem to want to implement this. There are obvious significant technical hurdles to overcome to work out how to handle update requests online and serve up updates if needed, but this is clearly the way to go. Some Symbian apps aim for a halfway house, checking for updates and displaying the result on a web page, rather than in the app, so that at least you're in the right place to make the download, though we're then back to things being rather manual and not quite as ideal.
It's worth noting that a similar small number of Android applications also 'dial home' for updates in this way, but again these are very much the exception rather than the rule.
One possible disadvantage of the auto-checking for updates is that the user might incur extra data charges, but I'd dismiss this by noting that a) update checks rarely involve more than a few kilobytes of data and b) if a programmer is clever enough to implement auto-update checking and downloading then he's clever enough to also check that the user is connected via Wi-Fi beforehand.
How many other Symbian applications emulate Gravity and automatically check for updates online, with no involvement from the user or any need to boot up the web browser? I'd love to know. I'm guessing only a handful - can you help out in the comments below?
The best and most comprehensive solution all round is probably to have the best of both worlds. An app store which tracks version numbers and can flag up any updates plus independent version checking by the apps themselves, direct to the developers. In truth, each system has its advantages, but as they're not mutually exclusive then why not have both in place, to catch all users, whatever their app usage pattern?
Steve Litchfield, AAS, 30 August 2010
News Discussion
Opening it up to *all* symbian OS devices (not just Nokia branded phones), would be a necessary step. The other major steps were recently made (simpler/cheaper signing process, uploading new versions, etc).
I've been using Gravity for over a year now, and while the application's auto-notification of updates is brilliant, I find that directly following the author (@janole) gives us faster access to the updates. He posts links to new versions more often than he updates the Update tab. Of course, this is for pre-Alpha versions, so that is not unexpected. (A nice feature that he could add would be a preference option for "give me scary updates" vs "give me released versions" in the Updates tab. Would make sure that the average user is recommended only tested and vetted versions, and would allow advanced users access to bleeding edge versions.
All the devs do is update the version in the repository, and mameo automatically notices the new version and shows updates available in the n900's notification area.
WIN.
I find Gravity's system great, but it can be easy to notice that an update's waiting for you, if your focus is on open app > check twitter > check facebook > read news > close app.
I'm also somewhat bewildered by Nokia's glacial pace of development of the Ovi Store client with regard to update notifications, since they implemented an update application for system software.
Another option is the one followed by one software publisher - I forget who - who demanded registration with an email address, and then justified that by emailing an updated *.sis file to registered users. If you've got on-device email set up, that makes things even easier.
Personally, I don't think that any application which needs network access to function has an excuse for not regularly checking for updates - and that doesn't include an option to open Web and check manually - and it is in the interests of all developers to provide an easy update route for users so users respect the developer and don't lose faith if they find a bug or have been waiting for functionality improvements.
Since Nokia hasn't done this for you, and more importantly since Symbian =\= Nokia, despite what the uninformed may assume to the contrary, developers need to do it for themselves.
|
Originally Posted by j d
I would argue that Maemo does this better than any mobile OS.
All the devs do is update the version in the repository, and mameo automatically notices the new version and shows updates available in the n900's notification area. WIN. |
I realise that I am probably not the norm not everyone would have as many apps, but even so, I would have loved to have had the same function on my Symbian phones.
Android Froyo allows users to update softwares all at once, I wonder why the author mentions it so passingly (atrocious word I know). Yes you may argue that 'Android is fragmented' (so spoketh a Symbian user!) but Froyo is being pushed out to all sorts of devices, even the D1, through rooting and ROMs, and installing custom ROMs on Android is easier than ever.
Symbian, oh symbian. Firstly, the platform is fragmented. Secondly, the 'flavours' of the OS are fragmented according to the maker's brand. Thirdly, the Ovi store is fragmented according to device. Fourthly, the devices are fragmented according to regions. And why bother, since most apps are not worth the trouble of using a Symbian phone anyway.
I SO wish Nokia adopt Maemo/Meego as their platform of choice. Maemo, despite on its last legs, is as good as Android and better in some respects.
Basically all LCG apps can check and automatically install an update if its available also the UC browser can do the same thing.
I can see benefits to applications self-updating, such as access to betas, and for many it works well. But it does require far more button presses in the long run compared to a centralised update all option.
However, the main reason to have a centralised updating mechanism is because it's safer. Say I'm an evil hacker and somehow compromise the servers of an app that self-updates. I put up a fake update with some kind of malware in it. You see an update, you install it, you send me premium rate text messages or something.
I'm not saying that scenario is impossible on the App Store just that you need to get an application approved first and that extra step adds a layer of security.
Of course app stores being the only method of installing apps is another kettle of fish...
Sorry, you're wrong. The only way to update binaries is through the software-install mechanism. Updates need to be signed as well. Taking updates from a developers server is no more or less dangerous than taking an app from there in the first place.
You say that app-integrated update might be a good thing and give 2 advantages:
1. the user doesn't have to lift a finger
Your example would mean that you start an app, intending to use it, instead your workflow gets interrupted by update process - restart of app etc.
For me, true definition of 'doesn't have to lift a finger' approach is system as implemented in Android 2.2 at the moment, when you check whether app should be able to update automatically and from that point on, you don't do a damn thing. It's always up to date. Even better would be if this option were on by default (on wifi), so mainstream users would have apps always updated. IF (stressing IF) you feel the need, you might install latest alpha/beta as apk package file, same as in Symbian.
Iphone OS is close, but doesn't have the automatic update capability as far as I know...
2. updates obtained from the developer's server will be bang up to date
True, but there are two major problems with this:
1) You might not always want to go for the latest, greatest alpha version available. With Gravity, this works because janole is such a great developer, but even with him there were several times when one update was following the other, fixing something broke in the previous alpha.
2) How do you get the information? Certainly, you can follow social media channel - twitter etc. of the developer. But honestly, regular Joe the user doesn't even perhaps know what twitter is, and surely you cannot expect mainstream users to follow app developers for such simple task of keeping apps updated.
I have some 70 apps installed on my phone at the moment, following just 2 or 3 devs. For entirely different reasons than updates :)
I can see the approach perhaps working for you, since you're interested in Telco, but for normal users this is simply too complicated, time consuming and awkward to use.
I didn't write this to do some Symbian trolling that's so popular nowadays, but in hopes that Symbian folks will stop whitewashing Symbian's faults and try to push it to reach level of other modern mobile OS.
payaxy
(previously Symbian, now happy Android user)
What's more : also (in my case using Opera Mini) one can visit the website to check the current version and download the file to the filemanager first . From there the install can be done .
This way you can store the old version . It is of great benefit , when the Updated version has glitches , which are not on the former version .
Shortly : from filemanager I reinstalled X-Plore 1.42 after I found glitches in V. 1.45 .
:) Regards jApi NL
|
Originally Posted by talhamid
I agree that N900 has the best way, but it is hampered by a slow manager, also the interface itself is not very user friendly.
Android Froyo allows users to update softwares all at once, I wonder why the author mentions it so passingly (atrocious word I know). Yes you may argue that 'Android is fragmented' (so spoketh a Symbian user!) but Froyo is being pushed out to all sorts of devices, even the D1, through rooting and ROMs, and installing custom ROMs on Android is easier than ever. Symbian, oh symbian. Firstly, the platform is fragmented. Secondly, the 'flavours' of the OS are fragmented according to the maker's brand. Thirdly, the Ovi store is fragmented according to device. Fourthly, the devices are fragmented according to regions. And why bother, since most apps are not worth the trouble of using a Symbian phone anyway. I SO wish Nokia adopt Maemo/Meego as their platform of choice. Maemo, despite on its last legs, is as good as Android and better in some respects. |
Today I became completely hacked off with my Android phone that I am trying to persevere with and have gone back to the iPhone while I wait for the new Symbian ^3 / ^4 stuff to arrive. All the hype and bull about Android and in my experience it is complete crap. I find it halarious how many criticisms of old Symbian are equally valid against Android.
I used the Nokia AU site to try and find prices for a new phone, just to check how much I would need when I do upgrade in six months time perhaps and I could not find a way on the site to buy an unlocked unbranded phone from Nokia AU so I did not end at the mercy of some indifferent carrier.
As for third party apps I download myself, I usually only look for an update for symbian apps if I have a problem. For my iPad I regularly check for updates and download them to my computer then update the device through iTunes when I next sync it.
I am more willing to update my Apple app store stuff due to the simplicity of the process. I have had issues in the past with symbian apps not installing correctly and needing to install a second time to get it right.
|
Originally Posted by brendand
@Biggles,
Sorry, you're wrong. The only way to update binaries is through the software-install mechanism. Updates need to be signed as well. Taking updates from a developers server is no more or less dangerous than taking an app from there in the first place. |
|
Originally Posted by Biggles
A high proportion of Symbian users hack their phones to install unsigned apps
|
|
Originally Posted by Biggles
Assuming that all applications are signed. A high proportion of Symbian users hack their phones to install unsigned apps, including ones that update themselves.
|
There are several other reasons why people hack Symbian phones, but circumventing the whole infuriating signing process for cool and powerful apps from developers too low-key or frustrated to sign themselves is definitely at the top of the list.
Just look at how popular jailbreaking is on the iPhone, as well.
Well, installing an unsigned update on a hacked phone can be as safe as downloading updates from an appstore if you follow the 2 golden rules:
1. Don't be the first one to update. First, let others in the symbian underground scene (or hacker communities if you insist!) try the update. If they show a green signal, you're good to go. And normally this 'testing' process takes a few hours, so its no big deal.
2. Always keep a backup of important data. In this way, even if you mess things up, you're only a hard-reset (and an hour or two) away from recuperating. This is more of a last resort, but by following rule 1 carefully you can almost negate this possibility.
And for an example of safe unsigned apps, look no further, the HX firmwares are the best example. They are not apps, but they are theoretically able to do much harm as they get into the system core. Yet, they are 100% safe. Back to the topic, Google maps also notifies of an update automatically. Count it in.
Also, I'm quite sure you're overestimating the prevelance of that practice anyway - regardless of the operating system in question. It's more common amongst iOS users I would say due to the huge amount of restriction Apple place on the system.
Only if you call 0.001% a high proportion... Give me strength.... [FX: sighs]
Devs who doesn't want to use the Ovi Store have to develope their own update mechanism in every case, so I see a two way strategy:
1) Ovi Store provides updates as painless as possible
2) Apps which doesn't come from the Ovi Store do their own thing
|
Originally Posted by Biggles
A high proportion of Symbian users hack their phones to install unsigned apps, including ones that update themselves.
|
|
Originally Posted by ClockworkZombie
The one thing more likely to send me to iPhone and not Symbian/ Maemo for my next phone is the handset firmware updates coming to the user at the mercy of the carrier they purchased the phone from. I wish Nokia could do the same thing.
|
|
Originally Posted by ClockworkZombie
I am more willing to update my Apple app store stuff due to the simplicity of the process. I have had issues in the past with symbian apps not installing correctly and needing to install a second time to get it right.
|
I've had plenty of App store installs on my iPhone where the install has just stalled and needing to be restarted. Also apps that have installed but immediately exit when they launch requiring a reinstall. All on my "perfect" iPhone.
Search
Navigation
Social
Advert