Nokia have made a number of developer announcements today, which significantly strengthen their developer services and offerings. Perhaps most interesting is news of a public beta service that allows developers to get their content Symbian Signed at no cost (compared to a first time signing cost of up to $215). Also important is the news that individuals can now register as Ovi Publishers (previously restricted to companies) and the Ovi Store is now accepting Qt based applications. Finally, and the most significant in the long term, is the first full release of the Nokia Qt SDK 1.0 and the accompanying Nokia Smart Installer (previously in beta). Read on for additional details.
Read on in the full article.
Again the Flagship N97 is left out of the supported list
Will WRT-Stuff work on MeeGo?
Yes WRT will be available in MeeGo - Meego 1.1 I think it is (check the roadmap). There are some changes in packaging compared to current WRT - moving towards the W2C standard I believe - that applies to Symbian^4 as well.
Maemo (i.e. N900) does not support WRT.
No WRT, doesn't work on MeeGo. At least not by default. You could still wrap your WRT app in some Qt application using QtWebKit.
Arrggghhhh! Still not possible to upload Python programs :-| Python for S60 is the master piece of Nokia. (At least) The Runtime should be included in any new S60-Phone. Python enables most people who have programming experience in any language (BASIC, OPL, C, C++) to write excellent programs for S60. Please note: Even if you can program in C++ (like me), that doesn't mean that you can program for Symbian. It's a steep learning curve and installing the SDK is a nightmare (you need a special Active State PERL version, which is no more available, need the GNU-Development chain, ...).
With Python you install Python 1.4.5 (because of PED) and Python 2.0 on your phone (2.0 also on your PC), install the Python IDE PED (on your phone!). Then you write your scripts on the phone, start and test it directly from within PED. When ready, you test it with 2.0, send it to your PC, where you have installed the Python-Kit from Nokia, start the PyS60 Application Packager (GUI-Program) and create a ".sis".
For the first time you distribute your programs, currently (at least for S60 3rd FP1) it's necessary to deliver the Python Runtime and pips.sis (included in the PC installation), which any user must install, before he can install Python scripts (afaik for 3rd ED FP2 onwards it's possible to include runtime and pips in the sis). It's really that simple. You can find some examples from me on http://www.aikon.ch in the "Programmierer Forum". The runtime is in Calcapp.sis, the other program is a interface to the Symbian inbuild SQL database. I have both tested on Nokias RDA on N97 (S60 5th), they worked - I am using an E90 communicator.
Last but nut least: Python programs using appuifw (you can also write command line programs) look like native S60 Applications and start much faster than Java-Midlets.
Peter
Fights back against whom? Do you mean Apple or Android? I would say the battle is pretty much lost.
The battle perhaps, but the war not. Symbian has 100+ million new troops (i.e. phones/devices) entering the battle field every year, on top of the 200+ million (probably more) troops they already have there. Any supplier of ammunition would be stupid to completely overlook that kind of potential.
Unregistered wrote:Fights back against whom? Do you mean Apple or Android? I would say the battle is pretty much lost.
Then you have a very negative attitude and I wouldn't have someone like you on my team.
Interesting definition of 'lost' when Symbian is still market leader.
Instead of saying symbian has lost, I think symbian is an untap market.
With an estimate of 500 million symbian phone on at the same time (based on IMEI), I think symbian is a great untap market, since ovi store just born.
A smart developer will try to cash in this untap market as soon as possible.
well,
I need to stop writing here and start coding 😊
As a developer I don't like the introduction of free symbian signing, without the need for a publisher ID. This will mean that in short time the OVI Store will be filled with thusands of crappy content, made by non-professional developers. 215$ to start a business is still a very low fee, and was effective to keep out kids and non-serious developers (most of them chinese) from filling the market with crap or low quality clone applications. Not a good move in my opinion.
@Peter Sulzer:
The whole idea with the new Qt SDK is to get rid of the old Symbian API and Symbian C++.
Qt is based on Open C/C++ and the IDE and SDK is really easy to install and use, it only took me 10 minutes to get everything up and running, including on-device debugging and everything. It is really great.
Application speed of Qt programs is native.
Python's interpreted approach is slow.
/Henrik...
Unregistered wrote:@Peter Sulzer: The whole idea with the new Qt SDK is to get rid of the old Symbian API and Symbian C++.
To get rid of S60 and the old Avkon library.
A big background on Murtazin Symbian^3 review, and why he does that to Nokia http://tinyurl.com/38he2dr
Also read:
Some truth about Eldar Murtzin review of Symbian^3 http://tinyurl.com/35wd7ow
@ the Unregistered developer,
well, there is still at least this to keep the most ameteurish developers out, no?
"the only up-front cost for developers distributing via the Ovi Store is a one off �50 fee to register as an Ovi Publisher."
"As a developer I don't like the introduction of free symbian signing, without the need for a publisher ID. This will mean that in short time the OVI Store will be filled with thusands of crappy content, made by non-professional developers."
Sounds like another store I know of..
Isn't that the sole metric of store success tho? :P
Unregistered wrote:@Peter Sulzer: Qt is based on Open C/C++ and the IDE and SDK is really easy to install and use, it only took me 10 minutes to get everything up and running, including on-device debugging and everything. It is really great.
Application speed of Qt programs is native.
The problem with Qt is, that it AFAIK doesn't run on old devices, like the E90 Communicator and it's not true Symbian C++. BTW: If there isn't a true successor for the E90 till end of the year, I will most probably leave Symbian and go to Android. I love Symbian (owned a Sinclair QL with the excellent Psion Office suite), but while the E90 have had the best hardware (especially the largest display) of its time, the new Symbian devices are no more up to date. Android and Windows Mobile devices are available with resolution of up to 848x480 and the new Symbian phones with touchscreen (and touchscreen is a MUST HAVE - even the Psion has it), have just a low 640x360 (the Psion has had 640x240 nearly 15 years ago).
Unregistered wrote:Python's interpreted approach is slow. /Henrik...
Not really. Normally you just call Python APIs which wrap Symbian APIs. E. g. to view a photo. The (native) Symbian code, which Python calls, requires much more time than the few if/while-statements or Python function calls, your Python program requires. A_N_D_: There are a lot of applications which don't require an ultra fast programming language, like e. g. my Calcapp calculator (with expression parser, variables and history). Even for the Psion 5 there is the excellent Macro5 utility which is mainly written in OPL, and most Psion user have it installed. Or as another example take the Handwriting Calculator from Nokia Beta Labs. This program could also be written in Python (from speed reasons), because the most processing time is taken by the handwriting recognition of Symbian. If there is an API in Python, you could use it - you won't recognize much difference in speed. The most Google Apps in the Web are written in Python, ...
Peter
It's nice that Nokia is striving to make their platform developer friendly, but that's not enough.
They have to do what Microsoft is now doing to lure developers to Windows Phone 7: pay them. Not with promises of prominent placement in the Ovi Store and development tools, although I'd include both of those.
I'm talking, literally cutting developers big checks with lots of zeros at the end, i.e. throwing bags of money at them to bribe them to develop for your platform.
Microsoft is now doing this, emulating their strategy of attrition with the X-box against the Playstation by spending, and spending, and spending some more until your competition says 'no mas'. Nokia should be doing this as well.
"This will mean that in short time the OVI Store will be filled with thusands of crappy content, made by non-professional developers."
Well the current system hasn't prevented the Ovi store filling up with thousands of crappy applications, so Nokia may as well try something new, God knows they need to do something fast.
If you compare the Ovi store to the iTunes application store and Android Market there is a huge gulf in quality between Nokia's platform and Apple's and Google's. There are literally hundreds if not thousands of great applications for the iPhone and Android, there are maybe only a few dozen genuinely competitive Symbian applications, and an awful lot of dross.
Nokia need desperately need to regain developer mindshare.
"To get rid of S60 and the old Avkon library."
Yes, sorry. You're right, got my definitions mixed up.
/Henrik...
"The problem with Qt is, that it AFAIK doesn't run on old devices, like the E90 Communicator and it's not true Symbian C++. BTW: If there isn't a true successor for the E90 till end of the year, I will most probably leave Symbian and go to Android. I love Symbian (owned a Sinclair QL with the excellent Psion Office suite), but while the E90 have had the best hardware (especially the largest display) of its time, the new Symbian devices are no more up to date. Android and Windows Mobile devices are available with resolution of up to 848x480 and the new Symbian phones with touchscreen (and touchscreen is a MUST HAVE - even the Psion has it), have just a low 640x360 (the Psion has had 640x240 nearly 15 years ago)."
@Peter Sulzer:
Qt DOES run on older devices - I test my code on an N97. The newly released Qt SDK works with Nokia's Smart Installer, so that e.g. older devices will get the Qt libs downloaded automatically if they are not installed on the device. Of course they still need to add more devices to the distribution support on Ovi Store, but right now N97Mini and X6 are supported. More S60 3rd and 5th will be added. So yes, Qt runs just fine on older devices.
I am not sure what your point is with "it's not true Symbian C++". I see this as a good thing, since Symbian C++ is horrible to work with in my opinion. Qt is based on Open C/C++, which is closer to what most developers consider the standard, and it performs exactly as well.
Besides being able to write native applications for both Symbian and Maemo/Meego from the same source code and just re-compiling is genius.
Qt is available for all devices going back to S60 3rd Edition FP1 - with a couple of exceptions (which I think are certain North American operator specific variants). Qt isn't real Symbian C++, but it is implemented in real Symbian C++. The best way to describe it is as a 'framework' (i.e. a set of APIs and concepts standard across platforms). It's definitely, definitely NOT a runtime.
As for the idea that reducing the initial cost will bring a slew of rubbish apps, this doesn't seem to have done Apple or Google any harm. Apparently consumers get confidence from large numbers. I would expect that the best way to keep out low-quality 'spam' apps is something close to what Apple do (but without an agenda behind it) - that is, an approval process. Hopefully fast and fair to the developer, but an approval process nonetheless.
As in iPhone user I can confirm that I delete 90% of apps within 5 minutes of downloading them from the app store.
brendand wrote:
As for the idea that reducing the initial cost will bring a slew of rubbish apps, this doesn't seem to have done Apple or Google any harm. Apparently consumers get confidence from large numbers. I would expect that the best way to keep out low-quality 'spam' apps is something close to what Apple do (but without an agenda behind it) - that is, an approval process. Hopefully fast and fair to the developer, but an approval process nonetheless.
I don't agree as to disallow the low quality apps with your way. It would hurt some newbie with great idea.
but, I agree that apps need to be regulated. I hate to say that when browsing the fruit company apps store and also ovi store, I wouldn't know the quality of the games/program I'm gonna to download.
I think that nokia need to develop more than 3 star or 5 star rating system. or maybe nokia need to put information in the ovi store such as:
1. java apps, flash, native symbian or native QT.
2. optimize for 120x160? 240x320 (qVGA)? nHD?
3. Free version? apps supported version? required internet? etc?
Sorry as this is not exactly on the same topic, but Rafe any AAS comment on the following biggie:
http://www.reuters.com/article/idUSTRE65N20Y20100624
"
Nokia's next flagship smartphone, the N8, will be the last N-series phone running Symbian software.
"
"
"Going forward, N-series devices will be based on MeeGo," said Nokia spokesman Doug Dawson.
"
I completely agree to Peters comments regarding Python for Symbian/Nokia.
Python adds an important facet to the many ways to create applications for Symbian devices.
Although it's understandable that Nokia wants to focus there developer support efforts on only a few solutions, they completely miss the point that there are a lot of non IT professional, spare time, hobbyist developers out there looking for an easy to learn, easy to code and inexpensive development environment. Python for Symbian is exactly this.
Have a look at the Python on Symbian book, currently evolving on the Symbian website, to get an impression how easy to understand Python code is and how fast you can create applications with Python for Symbian devices.
http://developer.symbian.org/wiki/index.php/Python_on_Symbian
If you are still not convinced, have a look and try some applications created with Python. A starting point is the PyS60 application list on Forum Nokia. It's far far from being complete, but may give a first insight.
http://wiki.forum.nokia.com/index.php/PyS60_applications
Although Python for Symbian currently has some relevant issues, it is possible to create apps that can't be distinguished from native apps by the end user in any way (despite the need to install the runtime...). The issues that should be solved immediately are:
- On most devices the user has to install the Python runtime and the PIPS library by themselves. Python 2.0 apps shows meaningful error messages when some dependencies are not installed and on some recent devices the runtime installation is started automatically. Nokia Smart Installer recently introduced for distributing the Qt runtime could be easily adapted to serve the Python runtime, too. http://wiki.forum.nokia.com/index.php/Nokia_Smart_Installer_for_Symbian
- Scrolling in listboxes on Symbian^1/5th Ed devices with kinetic scrolling isn't working correct.
Martin
PS I wrote a lot of Symbian apps with Python. Few of them are published, see: http://www.md-soft.info/
Unregistered wrote:This will mean that in short time the OVI Store will be filled with thusands of crappy content, made by non-professional developers. 215$ to start a business is still a very low fee, and was effective to keep out kids and non-serious developers (most of them chinese) from filling the market with crap or low quality clone applications.
Frankly in my opinion, so far the Ovi Store
is filled with crappy content. Not thousands, but what's there is in the majority, rubbish.
In fact I'm amazed at the poor quality given the previous need to be a "business" to do apps, but then it costs virtually nothing to get a registered company, at least in the UK (I know, as I'm a contractor).
There has also been some rather dubious apps with suspicious activities (one I reported along with a lot of others because it was doing call backs on a premium number without permission or informing the user!).
I don't trust apps in the Ovi Store. Most have over inflated opinions of their features, and in general are not reliably compatible with all phones, even when they do advertise as being compatible with yours. Having to spend money on an app only to find it doesn't work and there's no one to contact or the "business" web site for the app looks like one of those shoddy malware or crap ringtone peddler web sites.
I welcome community apps. Yes there will be rubbish, but there will also be quality stuff, open source hopefuly, from people who care and enjoy creating applications, instead of from companies who just want to churn out crap and charge a fortune for it, because until Apple came along, they realised it was easy money from gullible fools.
Oh, and there are a few exceptions in the Ovi Store. Ovi Maps, Sportstracker and Gravity.
Maybe apps will need to be vetted though to weed out anything that will break your phone, but so long as it doesn't go as far as Apple in restrictions.
Peter Sulzer wrote:Arrggghhhh! Still not possible to upload Python programs :-| Python for S60 is the master piece of Nokia. ...
Peter
I completely agree and I am going further to say Nokia MUST include JAVA if this war is to be won.
Normally we should just watch these commercial wars but this time is different. And I felt so compelled to register just to say this. At least this site there are many good sane folks.
If Apple gets its way it will mean all the struggle to go Open source wash down the drain. Not only that Apple is trying to also wash down all existing de facto standards in THEIR name of better iPhone efficiency.
It used to be that for developers to look at the install base of desktop computers and decide to invest on a sensible platform. Years ago it got to be Windows locking out better apps. With the help of JAVA and to some commercial extent Adobe Flash, the web-based apps could flourish freed from Mac and Windows. Now the equation have changed with iPhone OS. One has to look at the install base # of mobile phones because that is what our users will enter the digital world.
This now means Nokia is not facing a hardware driven strategy issue. It is at this MOST important historical juncture to decide the future of computing development. Unfortunately, Symbian libs though efficient but was never prepared this big task. This is why a higher language like Python is so important.
An analogy will be DBMS like Oracle, DB2, Informix. Only until their introduction of 4GL on these DB platforms that good commercial apps start to flourish and revolutionised the corporate apps. The reason is simple: apps developers cannot afford the time to deal with unnecessarily low level details. That is why COCOA from Apple make a lot of sense but still not good enough.
QT is a good effort but I see it as implement useful class libs for other high level developers to use. Nokia must now decide how to reign in all developers with existing OPEN skills.
Unregistered wrote:1. java apps, flash, native symbian or native QT.
2. optimize for 120x160? 240x320 (qVGA)? nHD?
3. Free version? apps supported version? required internet? etc?
Well said. Esp for Symbian apps need to differentiate between s60v3 or v5 compatible or v5 only. A lot of v3 apps are crashing the v5 devices and gave the n97 a bad name for example. Nokia have to remember that a lot of non-symbian savvy users are attracted on board due to the newer touch-based devices.
Java! Java! and allow all Symbian devices to connect to Ovi, not just Nokia ones. I mean there were tons of ready java games out there.
Ovi is just not one type of codes unlike iApps, it must stand for OPENness and not OPEN MADNESS.
samson432 wrote:
... The reason is simple: apps developers cannot afford the time to deal with unnecessarily low level details...
I also agree that Nokia should be more open to new developer offerings.
Then when I read samson432`s comment, just wanted to mention my problem about time...
I am dealing with this WRT project for my studies and during my presentations, I will have to make changes in the code and show the results on the app more than 1 time.
But I have limited time for the presentation and it wastes so much time to send the app to the device and reinstall it everytime.. Am I too impatient or does anyone else have such time issues reinstalling WRT widgets??