phranque
msg:3362417 | 6:56 pm on Jun 8, 2007 (gmt 0) |
there is no "standard" yet.
the state of the art is in flux.
javascript enabled mobile browsers are not the norm.
at this point, the best place to start is probably WAP.
|
music_man
msg:3362602 | 1:17 am on Jun 9, 2007 (gmt 0) |
Thanks for your reply. I'd like to use something like Ajax so that the page doesn't need to reload for every request...
|
phranque
msg:3362620 | 2:25 am on Jun 9, 2007 (gmt 0) |
it partly depends on how much mobile market share you are going for.
some phones are java enabled which may work for your application...
|
jtara
msg:3362956 | 5:45 pm on Jun 9, 2007 (gmt 0) |
It depends on just what you call a "mobile application", and whether your target is phones or smart phones (e.g. PDA phones). It sounds like you want to develop an application that won't use airtime, at least part of the time. That rules out WAP. Most GSM and some (in the U.S. only a very few) CDMA phones can load Java applications. Most CDMA phones can load Brew applications, which typically have to be approved by and sold through the carrier, and are typically written in C++ (though there's no specific language requirement - they are compiled to machine code.) "Smart", or PDA phones can load applications written typically in most any language (as with Brew) and using the APIs of their respecitive operating system. (e.g. Windows Mobile, PalmOS, or - emerging - flavors of Linux).
|
brycen
msg:3370504 | 12:58 am on Jun 18, 2007 (gmt 0) |
You face more barriers than just technology. The wireless carriers control the browsing experience for many users, it's a "closed shop". You need a relationship with the carrier to get your content seen.
|
|
