Subscribe to RSS feed
Follow me on Twitter
Follow me on Facebook
Follow me Google+
Tag Archives: nokia
Testing mobile sites on Nokia Series 60, Series 40 and Meego (Mobilizing websites with responsive design and HTML5 part 13)
This blog post is a part of Mobilizing websites with responsive design and HTML5 tutorial. For all posts please see the Introduction post.
This blog post gives you intro how to test mobile sites in Nokia phones, with one exception. Windows Phone phones will have their own blog post following soon after this post.
1. Series 60 and Meego
N8 is the most notable Series 60 phone. Though Series 60 is at the end of its life, it still represents around 30% of world smartphones. Series 60 was the first OS to use WebKit, but unfortunately Nokia decided to develop its own Web Run-time Javascript based development environment instead of focusing delivering good HTML5 experience on the browser. Sadly, HTML5 experience is not that good, but acceptable, somewhere little bit behind Android Browser.
N9, the best phone in the world, is the first and the last Meego phone ever produced. It’s market share is unknown. Most developers prefer this phone due to its Debian/X11 based operating system. You can apt-get install software into your phone.
2. Remote Device Access
Nokia has remote service to access Meego- and Series 60 (Symbian) phones in a publicly accessible “phone cloud”. This is the recommended option for testing your mobile site on these phones unless you have a device yourself. This service seriously kicks ass and I hope other vendors would provide such free service for developers.
Remote Device Access cloud accessible phones are real devices, not emulated ones.
The service requires
- Sign Up
- A web browser
- Java run-time, with Web Start bootstrap. Note that the service uses Java Web Start, not Java applet, though it does not make any difference.
Remote Device Access does not have Windows or Series 40 phones as writing of this.
When you open the service you can request ~30 minutes usage time for a device and remotely access it over Java application. The phone is fully yours, there really aren’t any limitations (beside making calls and such).
N9 running in a window from Nokia Remote Device Access service
There is some lag when using the service, but you can can withstand it to get the mobile site testing done.
3. Series 60 simulator and SDK
Series 60 simulator is based on recompilation of Series 60 components for Windows and emulating some Symbian OS features.
Some features of SDK
- Windows only
- Pain to set up
- Awful to use
Skip it.
4. Series 40
Nokia Series 40 phones are wide-spread in developing world due to their cheap price, physical durability and long battery life.
Nokia low end Series 40 operating system is closed, proprietary and not very portable. There does not exist much testing tools for this OS, outside the phones themselves.
Newer Series 40 phones have a WebKit based browser, older phones some proprietary browsing engines which really can’t do even the basic CSS.
Opera Mini, based on Java ME, is popular third party aftermarket browser available for Series 40 devices and making the web surfing actually pleasurable. You can recommend using Opera Mini for your Series 40 users.
These phones are cheap, so just buy the most popular Series 40 of your target market.
Subscribe to RSS feed
Follow me on Twitter
Follow me on Facebook
Follow me Google+
Mobilize.js version 0.9 released
It’s officially now so stable you can use it.
Some notes
- Opera Mini has issues, but has been proven to work perfectly in the past
- We don’t actively support Nokia devices yet, but they have been proven to work perfectly in the past
Thoughts about WP7
Now that Nokia made sure most of the energy put on Qt goes down the drain, I took a peek at Windows Phone 7 development and I was disappointed.
I posted a short comment to Future of Qt blog post and I thought I’ll write a bigger rant to make people more aware of an important issue.
The tools for WP7 are probably the best with Visual Studio and GUI editor and what else, I’m pretty sure about that, but the platform itself is disturbing: all code must be C#. You can’t use C/C++ with WP7. And when there can’t be those, there won’t be CPython nor Lua or any scripting language implemented without C# or .NET managing your code, unless you’ll find a C# port for it. And if you did, it most likely lacks in features compared to the original. And then there’s numerous other C/C++ libraries that you can’t use.
Somebody commented on my post saying this is the reason why the platform will fail and nothing except meaningless apps(fart apps,rss readers etc) will be ported. Apps with long history, existing code base and support for multiple platforms can’t be pure C#. And I agree 100%.
Microsoft wants to avoid fragmentation, well that’s good but not with these restrictions. Lack of “unmanaged code”, as native code is called in .NET land, will be causing fragmentation, not the ability to reuse your code. It’s your code that’s fragmenting so MS doesn’t care. This is even worse than the Apple’s ban on scripting languages, which was removed a while ago. They still allowed reusing old C/C++ libraries, like physics engines in your apps.
If WP7 ever gains popularity among major app/game makers, I believe and wish they’ll make this issue clear to Microsoft as they (I assume) did to Apple. Well, first they need to gain popularity among consumers 😉
Without knowing much about the internal workings of WP7, I don’t see reason to block native libraries. Sure, it’s harder to avoid dll hell with C/C++ as the problem is well known on desktop. But if my app doesn’t use any system libraries but only its own? How many system libraries do you think a physics library might need? How many system libraries does a Lua interpreter need? I can think of one: libc for allocating and freeing memory. All those libraries do is reserve some memory and do some math and give some results back. Sure scripting languages may allow file access etc., but that’s not necessary. I just want to script some logic of the app, not the whole app. Anyhow, I don’t see the point, somebody, please enlighten me. Google & Apple can do this without getting in your way, why not Microsoft?
I have been reading discussions about Nokia-Windows deal, and only fraction seems to think that the whole Nokia-WP7 thing is a good thing. And those who do seem to be… less informed. The only good thing here is that we are finally getting rid of Symbian, but the price is too high.
So what’s the main reason that I’m worried about: to force people use .NET and me to write only C#. We have now witnessed what happened to people skilled with Symbian C++, the fear that I heard soon after Nokia started using Symbian. So don’t try to get us stuck with a single way of doing things. Sure there’s monotouch and monodroid to reuse your code on iPhone and Android. Not sure about them though, not free and they add another layer of complexity to your app. Easier to just learn the platform’s own way. I have no trouble using C#, but that’s not the point: I want to reuse my old code and the other libraries out there. Apple is good boy compared to MS.
And my opinion about C#? Nice, but Qt Quick rules. Sadly, now I can only think that it should rule. *sigh*… back to the drawing board.