David Beers writes:
There is another kind of “mobile data” that strikes closer to the question of user experience and solving real problems. That is the data that is stored locally on the mobile device. While everyone is focused on what will drive wireless data usage, mobile OS vendors like Microsoft, Symbian and ACCESS have made some interesting changes in how your data may be stored on your mobile and what you will be able to do with it: each is baking a relational database engine right into the next versions of their operating systems.
One important kind of data that users generate constantly is rarely captured despite the fact that it is tremendously useful for personalizing and simplifying the user experience: data about usage itself. Information concerning how often certain pieces of information are accessed by the user or how they relate in actual usage to other bits of information should factor into how software responds to input. For example, if I’ve sent a lot of text messages to Linda this week it would be nice if my phone predicted that I was probably sending her another one when I entered just the letter “L” as the recipient and offered to autocomplete this information.