Want to know how the Asha UI looks like and read the UX documentation? Well, aren’t you lucky: here’s the link!
The Nokia Asha design guidelines provide a comprehensive set of UI component descriptions and UI patterns. For app icons, templates and guidelines are of course included. And to make things as simple as they can get, there’s also a UX checklist.
Stay tuned for more updates on the Asha UI in this blog. And don’t forget to check the Event calendar for Asha UI webinars!
This is a two-part article. The second part will be covered in a future post.
There are some fantastic styles available now in CSS3. Apart from anything else, border-radius and box-shadow alone are the greatest tools to be added to the web developer’s toolbox since
float:left. Alongside these highly important and commonly used attributes, there are also some new values for existing rules like background-size:cover.
There is a lot of talk around responsive Web design being too slow or too resource intensive and that other methodologies can achieve better performance. I don’t want to go into the details of which approach is better because I think different scenarios require different solutions. What is certainly true in all cases is that a Web site or app that loads faster is better than one that is slow. Companies like Google, Gomez and Akamai have all published papers and survey results showing how speed affects user perception of a service from your desktop computer and even more on a mobile device (KISSmetrics has also drawn a nice infographic for the lazy ones). This is the first article and another one will follow shortly. Continue reading
If you are thinking about monetizing your Series 40 application but reluctant go through those numerous In-application Purchase API’s boring guides, take IAP application template and use it in your project with minimal adaptation.
Save your time, focus on your project and leave IAP routine for me!
That is the main goal of the IAP application template project. Please try it and let me know how I can improve it.
Easing your digital life
I was always wondering, if streaming a YouTube video would work on Nokia Devices with Java ME. I was pleased to find out that it did! And it did, very well, over a 3G connection on the stunning screen of Nokia PureView 808.
The idea is pretty simple. All you need is a Canvas with a YouTube logo, a Video Window for displaying the stream and playback controls for starting, stopping fast forwarding or rewinding the video. The cursor is draggable so that it offers the same user experience as the standard YouTube player.
This wiki article, explains how.
30.07 I started porting FifteenPuzzle game project to Series 40 platform and today 10.08 that work is completed. Having promised to complete the project in 5 days I observe the golden rule of project management in action : multiply your project estimation three – two times before passing the estimations to your customer
But nevertheless… Meanwhile I have explored Scalable Graphics in Series 40 for possibility of applications localization and created a wiki article. FifteenPuzzle game project now contains SVG main menu and text in SVG document is translated to English , Finnish and Russian. The whole the application features list is the following:
1) main menu SVG
2) device language detecting and supporting automatically
3) SVG text localization
4) supports screen sizes:
240 x 400 Asha 31X
320 x 240 Asha 30X
240 x 320 Asha 20X
128 x 160 Asha 1XX
5) Disables SVG automatically on low-range devices (Asha 1XX)
Check it out
For those of you who need an activity indicator that displays a progress bar as an alert and dismisses itself when the activity completes, you might find it hard to use a high-level Gauge. Using high-level components for creating such an indicator is pretty easy and looks great on Series 40 full touch devices, as long as certain criteria is satisfied.
This article describes in detail how to code one.
If you are watching the wiki article series “Quick start in game development for Series 40”, this announcement for you. I am glad to say the series is complete. An application project complements the articles and shows how functionality is built up step-by-step. So it is convenient to examine the code difference to understand how it works. The latest project step is available for download from article “Game development for Series 40: Main menu implementation” or from here. The game path-finding and collision detection algorithms are left outside of the series. Perhaps i will return to that when i have time. So far it was good coding race and interesting platform exploration for me. I hope it is useful for you as well. Please comment and ask – each and every question will be answered.