Hi
>From: Shawn <javajunkie@koyuru.com>
>Reply-To: keitai-l@appelsiini.net
>Date: Sat, 05 Jul 2003 14:15:45 +0900
>
>
> KDDI says its BREW-enabled phone is its number-two-selling model
>(http://www.advisor.com/doc/09915). Whether or not that makes it a
>terribly likely direction I can not say. If there are additional financial
>incentives, who knows what other providers may do.
>
>My point is look at KDDI's web page. Their marketing clearly seems to
>favor brew IHMO.
I dunno about that. I specifically checked AU's page (the division actually
selling these phones as opposed to corporate KDDI) about the time of BREW
launch & again 3 months ago looking for evidence of "pushing BREW over Java
or vice versa". I couldn't see it then, and I just checked again now, and
can't see it now either. To me, their site (when reviewing their contents
intro pages & phone line pages) is quite agnostic- which makes complete
sense to me since they are in a unique position of offering two application
platforms.
>So over time while BREW may fade as Java expoited more of
>the phones capabilities, high costs are realized etc, it seems like small
>CP may very well want the jvm running on top of brew if possible. It
>provides a much more flexible way to get apps into a phone, and if BREW
>features are needed -- well they could consider that. From a users and CPs
>standpoint, having the flexibility both would seem best but from KDDI's
>perspective, I think we are talking a difference in revenue streams pulling
>them to push BREW (but I really don't know).
I think it is purely speculative to predict whether both systems will be
offered on the same phone. It could cause a lot of confusion for the user.
Its kinda like having two native browsers to choose from on the one phone
(may not be the best analogy). My impression is the KDDI/AU are testing the
waters about which technology is "preferred" by both users and CPs, though I
imagine they are getting a lot of pressure from Qualcomm to push BREW. The
reality is though, a lot of CPs have to gear up late in the game to support
a different platform that is more "dangerous" (flexible - depending upon
your view), anyway regardless) requiring relatively expensive testing &
certification. Compared to Java, I think this situation will obviously force
CPs to make a fundamental choice about their application strategy by now.
>At the very least, I would wish KDDI give some mention to java apps or are
>they entirerly insignificant?
I just had a look at AU's site, and checked out a section called "plus
alpha" content, and "What's your favorite things (sic)" (refering to a few
user's favourite content - probably paid users but doesn't matter). It
clearly shows Java technology as a couple of "favourite apps". If this was a
pure marketing push opportunity - they could have pushed a BREW app as a
"favourite app" (there are no BREW apps listed). To me this again shows AU
being agnostic about the technology choice. Even ordinary web sites are
listed as "favourite apps".
>Small CP who use java should be irritated
>that KDDI gives no indication that while BREW can run J2ME apps (through
>the bridge I believe), there are contracts to go through, and hoops, and
>hurdes and that is going to effectively reduce the useful apps to BREW
>users.
It may sound strange or pretentious but I think the "no indication" is
sensible. It is up to the CP to make the development choice based on current
or immediately foreseeable handset capabilities.
Regards
Michael.
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
Received on Sat Jul 5 13:57:55 2003