InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Motorola Challenges Java Developers to Rethink Mobile Computing

Posted by Chris Greenlee on May 11, 2007

Sections
Development,
Architecture & Design
Topics
Mobile ,
Java
Tags
Java One ,
Java ME
Thursday at JavaOne started with a thought provoking keynote by Motorola CTO Padmasree Warrior.  Rather than the usual vendor keynote making grand announcements or touting specific accomplishments of her company, Warrior focused on challenging Java developers to think hard about the transformation of the mobile world.  The theme for her talk was "Platform Disturbia", and she painted a picture of the current state of affairs in the mobile world, and challenged developers to rethink their approach going forward.

Key problems in mobile computing

Fragmentation: The mobile platform is fragmented in areas ranging from hardware, to the flavors of Java available on devices, all the way down to the level of compression formats and DRM schemes for media content.  

Feature overload: Starting with the integration of text messaging into mobile phones in the 1990's, every conceivable feature (for better or worse) has been integrated into phone.  While phone with cameras, flashlights, alarm clocks, email capability, and music may be great, they are often complicated and cumbersome.

Monolithic platforming: Developers tend to think about applications for the phone as extensions or variations of applications for the PC world, but the mobile world is completely different.  Warrior pointed out that when using a mobile device, users hands are not free, their screen is small, and they are frequently distracted.  Mobile users also tend to see their mobile devices as extensions of themselves, not of the PC.  As a result of these two factors, developers will need to approach mobile applications very differently from PC applications.

Transformative developments in mobile technology

WIMAX is coming, and Motorola sees it changing the landscape for mobile computing.  While skeptics have claimed that no one will want to watch full-length movies or television shows on such tiny screens, Motorola's research indicates that a significant percentage of commuters in southeast Asia want exactly that.  With commuting times averaging an hour each way, an increasing number of people are spending large blocks of time with only a mobile device for access to content.  Providing the bandwidth is only the first step, though, in serving these users.  

Personalization will be incredibly important, since greater capabilities for mobile devices will only add to their already overwhelming array of features.  Her point appeared to be that mobile users do not want a swiss army knife all the time; instead they want a tool that adapts to their situations.  The features that a person will want in the forefront at home will not be the same as those they need during their commute, or in the office.  Likewise, each person may have different preferences for the ways they interact with their devices.

Challenges to mobile developers

The essence of Warrior's talk is a challenge to developers to not only address the current problems with mobile computing, but to embrace the transformations that are coming in the mobile world.  In particular she called out four key areas for exploration:
How content delivery will be accomplished in the WIMAX world; specifically how developers will deal with transcoding and DRM
How the infrastructure to support broadband everywhere should look, from CRM and beyond
How and where personalization will occur.  What will it look like?  Will it happen on the device, on the network, or in the cloud?
How will socializing work, and how will it be framed for the user, since more and more will occur over mobile devices?
Verizon, Cingular and ATT by zqu dlyba Posted
Padmasree Warrior is CTO, not CEO by Chen Jackson Posted
Re: Padmasree Warrior is CTO, not CEO by Deborah Hartmann Posted
  1. Back to top

    Verizon, Cingular and ATT

    by zqu dlyba

    Verizon, Cingular and ATT have a lock on the distribution of applications sold to consumers today. Why would I want to develop an application for their proprietary network? If my application became popular, they would just steel the idea.

    I don't see third party application vendors making money in the existing proprietary networks.

  2. Back to top

    Padmasree Warrior is CTO, not CEO

    by Chen Jackson

    Padmasree Warrior is CTO, not CEO

  3. Back to top

    Re: Padmasree Warrior is CTO, not CEO

    by Deborah Hartmann

    Thanks, corrected.
    deb

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.