Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Wireless Networking Technology Hardware

Applications and Service Platforms For Mobile User 35

Roland Piquepaille writes "ERCIM News is a quarterly publication from the European Research Consortium for Informatics and Mathematics. The July 2003 issue is dedicated to research about applications and service platforms for the mobile user. All of the 30 articles are available online. This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations. Among other projects, you'll discover mBlog, "a mobile information service for all," or Fluid Computing, a middleware which lets "an application 'flow' from one user interface to another.""
This discussion has been archived. No new comments can be posted.

Applications and Service Platforms For Mobile User

Comments Filter:
  • Bigger Issue... (Score:5, Insightful)

    by mgcsinc ( 681597 ) on Monday July 21, 2003 @08:31AM (#6489977)
    While I recognize that it lacks relevance in the frame of the ERCIM newsletter, there is one particular problem plaguing mobile application and service providers: actual potential use by the customer himself. Issues such as special interfaces and differing platforms can be seen as unique design opportunities as well as challenges, and small availability of power, processing, and memory may be viewed as opportunities to weed out needlessly consuming code, but the general reluctance of even the most sophisticated enterprise users to take advantage of every mobile tool available - due both to the expense of mobile hardware and software systems and lack of true need for such tools - will remain a considerably more insurmountable obstacle for developers...
    • by tgma ( 584406 ) on Monday July 21, 2003 @09:13AM (#6490176)
      One thing that the last few years have shown is that once platforms are built, it's very hard to predict which ones will take off, and exactly how they were used. I think that the same will be true about mobile data.

      You are right to question the true need for such tools. How many of us really need to update our blogs on the bus to work? Of course, an account of a bus ride would be much more interesting than the drivel that you usually see in blogs, but you get my point.

      However, I have found one perfect application for my SonyEricsson P800 - it takes the public domain stock prices, and displays them in an easy to read screen. This is much easier than going to a web page, which is going to be full of graphics that I don't want. I don't really need to send emails or surf, but this little app justifies GPRS to me.

      I think that there is another question about whether this technology is going to be on the client or the server side. Designers may not be willing to adjust their code for every single device out there, even though I would dearly love to believe that XML can do this for them. On the other hand, if you can make a client side application that will strip out the useless information, or illegible graphics, this will ensure that content is delivered in a useable way. I think the app will have to be device specific: to use a trivial example, the mainstream games that have been ported to mobile devices, like Doom and SimCity, IMHO just don't work, because they were never meant to be used on such small screen real estate. It's very hard to anticipate every single quirk of every single device on the server side, so the work is going to be done on the client side, where the device knows exactly its own requirements.
    • Re:Bigger Issue... (Score:3, Insightful)

      by Surak ( 18578 ) *
      Lack of true need?

      When the personal computer revolution hit, there was a lack of a true need for PCs. Nothing that could be done on the early PCs at that time couldn't be done with some other method -- whether manual or electronic.

      It came down the killer app. And the killer app was spreadsheets. Nobody in the business world could IMAGINE this day getting by without a spreadsheet.

      The Internet wasn't needed either. The killer app -- universal e-mail. Our mail server went down on Friday and there was M
    • Re:Bigger Issue... (Score:3, Interesting)

      by Wellspring ( 111524 )
      I totally agree with this. I just got out of two and a half years spent working at a mobile application platform company, and so have seen the belly of the beast. Yes, the slow economy is the major reason for slow adoption, but there is another, deeper reason.

      For one thing, a key piece of the industry, the wireless WAN providers, are simply not ready for prime time. It is very difficult to deploy an application over the air, and mostly this is for bureaucratic reasons. Carriers require long expensive c
  • Fluid computing??? (Score:3, Interesting)

    by stonebeat.org ( 562495 ) on Monday July 21, 2003 @08:50AM (#6490073) Homepage
    Isn't that just another name for XML????
    • by GlassUser ( 190787 ) <slashdot AT glassuser DOT net> on Monday July 21, 2003 @09:08AM (#6490150) Homepage Journal
      Eh, not hardly. Think serializing a data stream while it's in use and farming it off to the same application running on a different system. It even works well on different architectures as long as the binaries read the same memory map the same way (watch out for low- vs high-endian issue, primarily).
    • by mmoser ( 468809 ) on Monday July 21, 2003 @09:23AM (#6490250)
      No, it's not just another name for XML. Its a name for the idea/vision that your application state can be migrated to (an)other device(s) at any point in time and even remain synchronized! I.e. you can not only migrate that document onto your PDA and then continue working on it during the bus-ride and later on your home PC (and back again next morning), but you could even share a document with other users at any point in time and changes by them could automatically be reflected in your copy.

      The name tries to visualize that transferring/sharing an application's state should be as easy as pouring a glass of water into another vessel.

      We were cought a bit by surprise by this early publication, so we don't have anything downloadable, yet. But we are working on it and there should be something available in a few weeks or so.
  • RTFAs (Score:5, Funny)

    by OoberMick ( 674746 ) on Monday July 21, 2003 @08:51AM (#6490077) Homepage
    All of the 30 articles are available online...
    30 articles! No one RTFA's as it is, nevermind 30
  • Global (Score:5, Interesting)

    by some1somewhere ( 642060 ) on Monday July 21, 2003 @08:52AM (#6490081)
    What I'm really interested in are things that work globally, not just in one or two countries.

    Just like in Japan... they have all these new funky 3G apps, that work no where else but Japan.

    When do we get services and apps that truely work worldwide (just like roaming GSM and similar, but on the app level rather than infrastructure?)
    • Re:Global (Score:5, Informative)

      by Talez ( 468021 ) on Monday July 21, 2003 @09:02AM (#6490122)
      A lot of the stuff is already cross compatible. Nokia for instance sells the same games worldwide via its Club Nokia service.

      Most other things would need to be localised or at least need local partners to provide the data that these apps need to function.

      As for video calls (3G's supposed killer app), I haven't seen any problems yet communicating internationally between 3G networks. For instance, you can make a video call between Australia and the UK and it works just fine (or at least Hutchinson/Orange says it does).
    • when providers and standards do not diverge for strategic reasons.
      On the beginning, 3G UMTS at 3GPP was supposed to be the unifying standard.

      Until US & Asia said, damnit, we're not competing with others. Lets fork 3GPP with 3GPP2 or whatever and have our own standard ...

      I guess this is not a technological reason. Like we settled on a worldwide PC hardware standard for untechnical reasons.
  • ...details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks...
    IOW, everything HTML was designed to fix. (Or if you prefer, everything that CSS, font tags, etc subequently broke.) [sigh]
  • ... I read the entire current issue and the other 35 issues currently available online?

    At a first glance, this looks mighty interesting. I cannot believe I have not come across this material before.

  • SkipWire was able to upload and download programs and data from any Palm OS wireless device.

    It did conversions between standard formats like .RTF, .DOC, .PDF, .JPG, .GIF, .PNG and the formats for the Palm, like PalmDoc, Fireviewer, TinyImage, etc.

    You could do everything from your Palm browser. You could convert both directions and e-mail. It accepted e-mail attachments, and then converted them and made them available for download.

    If you didn't have the right program to view the data, then it provided t
  • Here we go again....

    Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

    TRANSLATION:

    "I am a shameless karma-whore [weblogs.com] and copyright violator [weblogs.com]... OK, I'm just dancing around what I really mean: thief [weblogs.com]! This column [IT'S MY BLOG! AGAIN! DID I FOOL [weblogs.com] YO

Every nonzero finite dimensional inner product space has an orthonormal basis. It makes sense, when you don't think about it.

Working...