As I blogged about some days ago, I had to wait before receiving my Flash Lite Player for my mobile phone and that did just get me crazy. But now I’ve received my Flash Lite Player 2, so I can test my applications.
The first part that takes my attention was shared object as I thought that if application doesn’t have over time memory, they may be useless.
[kml_flashembed movie=”http://www.metah.ch/blog/image/soTest.swf” height=”332″ width=”281″/]
Shared Object are easy to manipulate with Flash Lite, here’s a little application that write something in your mobile memory (you tell him what to write). After you close and reopen the application the saved object is still existing (might be useful to keep some important information about the user).
The shared Object will only work on your mobile phone not on debug mode (but it will on a normal Flash Player 7)
To test this, just install this application on your mobile, write a word and click on Insert then quit the application. After you reopen it, the size of the Shared Object will appear, if you click on Test you will see what you had written before closing it.
[kml_flashembed movie=”http://www.metah.ch/blog/image/codeSwf.swf” height=”400″ width=”380″ /]
Download the fla
Here are the links for all Sessions of the Adobe Developer Week.
It’s seems that some are a bit slow, anyway this is a gold mine.
Here’s a little pattern I made for«homework» about the integration of usability in a website. Now that I’m nearly on holiday I found the time to transform it for Flash only.
Technical (about user system)
Accessibility (about user handicap)
Usability (user friendliness)
Refercing (about findability)
This pattern is more developer oriented (but can overlap the designer work).
Also these are the kind of thing « a bit boring » you don’t want to do at the end of a project (in my point of view).
I’ve cut the pattern in four entities:
What the size of the window where the browser is display? You don’t want a part of your site to be unseen. The content size must be adaptable until a reasonable limit.
The download speed of the user is important in the way you don’t want to publish high quality content to a 56 kb/s instead you give him a low quality (letting him the opportunity to change is a good usability point).
All this accessibility part must be taken seriously as it’s unethical that people with handicap can’t access information and soon illegal. Flash as some accessibility function, don’t forget to use them.
The eyes compatibility is to test that your user will see nearly the same thing (color change).
The size of the text must be resizable, small text are for some people unreadable.
You site needs to be readable by screen reader application, or it won’t be accessible to some people.
Heuristic has to be defined in the early development as some function has to be integrated in code).
User friendly means to not make people avoid to ask themselves « how do I what I want to do » it shall be obvious.
Backward and forward navigation is important to manage or people risk to be feeling uncomfortable on your website.
Html documents needs to be well meta-tagged and descripted.
Swf documents needs as well to be meta-tagged and descripted.
Important text can be over/under a swf. So search robots still can index your content (beware with Google politics about that).
A lot of thing could be added but I estimated that that was the main guideline to be follow for the user. Unfortunately all these things take energy, time and money but if not done, it really can kill your website.