The categories of core vs downloadable are based on commercial limitations and by extent technology limitations as well. For example SEMC handsets prior to JP8 don't make it possible for a developer to access the idle screen.

The core vs downloadable apps impact the user journey differently as I highlight.

The point you mention about APIs is true, but does not apply to 'sensitive' APIs that in many cases give developers more access to the screen real-estate and system events than the manufacturer feels comfortable with, for both branding and liability reasons.

Re: BREW and Nokia WRT: they both integrate with device APIs more than the average AE

Re: BREW and AppStore: Here I was comparing BREW and BDS with AppStore, which is comparing lemons with limes They are very well designed B2B2C and B2C channels respectively connecting developers with users.

Andreas

As a software engineer communication with the real world is not a feature from Deliver. What you name as Deliver is a list of capabilities, either basic or extended. And it's the main point in order to start studying the rest. I'd call it AE Scope: what the ae can and cannot do.

Core and downloadable applications can use exactly the same API. Other problem is the developing scope: if you're modifying bluetooth support, or you're just changing the icons and some menus in the default distribution package.

Outside the core (modified or upgraded) then you have the applications based on what you consider core libraries.

And the last thing commenting on your trends.

- Android is a risky platform. Before the last release, the SDK was closed and open only to few privileged human beings. The short and medium term investments are waiting for something more real.

- iPhone did the opposite. First the phone and then the SDK: "here is the real thingy, now you can think about developing for my platform".

- JavaScript is a bit dangerous some times if it's used with specific platform extensions. You need to have a clear vision of where you want to get applying that technology into your project. But the future for javascript is quite birght in safari 4 and firefox 3.1 (IE8 has to show it deserves something more than pre packaged compatibility hacks).

- Mixing BREW and Nokia's Web Runtime: should be forbidden to put them in the same sentence.

- BREW and Apple Store: comparing printers with bookshops.

Thats all

Tote, good comments, let me clarify:

- I meant that an AE can be primarily designed for either 2nd or 3rd parties. An AE can't be solely designed for 3rd parties, as 2nd parties will always get involved. However an AE *can* be designed for 2nd parties only (e.g. RTOSes)

- Symbian OS is a corner case. It was originally designed for 2nd parties, and gradually extended some of its APIs to 3rd parties.

- AEs designed for 3rd parties can use any language – you 're right, I 'll clarify the wording.

- Agree entirely on Android and I think I pointed this out on the post; Android may be open, but Android-based phones may be closed to limit OEM/MNO liabilities.

- Andreas

Nice post, though there are some things that I disagree with:

- First I didn't get what you meant on whether an AE is meant for 2nd vs 3rd parties: did you mean 'solely' or 'primarily'? For example, you can't say that Symbian is designed 'solely' for 2nd-parties, because there are lots of public Symbian OS APIs (not S60, nor UIQ) that 3rd-parties can use, too. This is the same reason why I can't say if these APIs are 'solely' or 'primarily' for xth-parties.

- Don't understand, either, how it contradicts who made an AE and whom it's designed for. Let's take Symbian, again, as an example: regardless of that Symbian OS was made by Symbian, I wouldn't say that it's for 2nd-parties only.

- Who said that the definition of AE designed for 3rd-parties is that it requires basic development skills only? It's ideal, I would say, but not essential.

- Android's idea about making the whole platform open in terms of being able to replace core applications, too, is nice. But I think we should wait what carriers will say on this and how it will work that the security system will rely on (dummy) user's decisions. The idea is nice on paper, but let's wait how it will work out.

Thanks!

VoIP not really mobile VoIP? Gerhard Fasol at eurotechnology.japan about 75% of mobile phones in Japan ship with digital mobile TV Gerhard Fasol at eurotechnology.japan about Last 2G phone shipped 8 months ago in Japan Andreas Constantinou atVisionMobileabout Application Environments: Order from Chaos Labels: AAPL

PlayPhone launches UK TV channel | Mobile Content | News by Mobile Entertainment provider teams with Top Up TV for PlayPhone Hits venture. Does iPhone Increase Browsing ? Iphone browsing stats are increasingApplication Environments: Order from Chaos[Flash, Web Runtime, OSX, widgets, Java engines, Python.. the array of software platforms is chaotic to say the least. Research Director Andreas Constantinou digs deeper into application environments, explains who’s what and identifies 5 clear