Opinionated comments on mobile phone industry news
|
All entries are written by Anders Borg, CEO and Consultant of Abiro, that has a long experience in strategic planning, developing embedded and Java software, usability aspects, and the mobile phone industry in general. You can also read the latest Mobile News entries on your phone via wap.abiro.com, and we provide many News Feeds from popular news services. For advertising and contribution queries, please use the feedback form. News feed (local) FeedBurner Feed
|
|
Monday, February 19, 2007
Use common sense when making mobile services
Update 20070301: The link is now correct.
The Secrets of Creating Great Connected Java ME Applications outlines that it's important to make use of the client and server capabilities in the best way possible, and is very much in line with the thoughts I have about the Mobilizer concept:
Update: I just read in the documentation for Visual Basic 2005 that also non-mobile enterprise applications are moving this way, where the pure web browser interface is considered too limited and not utilizing local PC resources, hence is replaced by local Windows applications (the way it was before, actually). I have to take Microsoft's word for it, but it makes sense: Enterprise applications that are completely browser-based tend to have terrible user interfaces. AJAX might fix some of that, but you are still at the mercy of the solution provider to make a consistent user interface across services. Something you get for free in Windows.
(via Mobility Weblog)
The Secrets of Creating Great Connected Java ME Applications outlines that it's important to make use of the client and server capabilities in the best way possible, and is very much in line with the thoughts I have about the Mobilizer concept:
- Client: user interaction, look-n-feel, etc
- Server: Number and data crunching, storage, etc
Update: I just read in the documentation for Visual Basic 2005 that also non-mobile enterprise applications are moving this way, where the pure web browser interface is considered too limited and not utilizing local PC resources, hence is replaced by local Windows applications (the way it was before, actually). I have to take Microsoft's word for it, but it makes sense: Enterprise applications that are completely browser-based tend to have terrible user interfaces. AJAX might fix some of that, but you are still at the mercy of the solution provider to make a consistent user interface across services. Something you get for free in Windows.
(via Mobility Weblog)
