but even there as I understand from others' posts, you have to be one of the 'approved' developers to get in. But the truth is, Android is effectively dead. So we have no other practical option. I am willing to bet that Google has relegated Android to a low priority project - at the same level as its zillions of small lab projects. IMHO it is going to remain dead for a few years and then be revived again when powerful phones become easy and cheap - a geek hobbyist's project.
On Jul 2, 2:50 pm, "Shane Isbell" <[EMAIL PROTECTED]> wrote: > iPhone has an established market so for the next 12-18 months it seems a > much better bet than Android. A major reason for backing Android over iPhone > would be getting an early mover advantage but without SDK updates that > advantage is lost. > > Shane > > On Wed, Jul 2, 2008 at 10:58 AM, Muthu Ramadoss <[EMAIL PROTECTED]> > wrote: > > > Apple can make it easy for us by letting Android run on iphone :-) > > > On Wed, Jul 2, 2008 at 11:05 PM, Mark Murphy <[EMAIL PROTECTED]> > > wrote: > > >> > Mark, > >> > thanks for clarifying. Objective C + Mac OS? > > >> At the moment, according to Apple's site for the SDK: "Technical > >> Requirement: Intel processor-based Mac running Mac OS X Leopard". Not that > >> OS X is a bad development platform -- lots of folk use it -- but it's an > >> added expense if you're not already on it. > > >> And, of course, Objective-C is pretty much just OS X and iPhone nowadays, > >> AFAIK. It's possible the iPhone will push Objective-C "over the top" so it > >> gets mainstream acceptance on other platforms, but I ain't holding my > >> breath. > > >> Here, though, is another place where a reasonably-open Android could give > >> us options. Getting Objective-C to work for Android is a matter of work: > >> create an Objective-C-to-JVM-bytecode compiler, hope said bytecodes are > >> within the set Dalvik works with, then create Objective-C wrappers for the > >> Android APIs (via SWIG?). While that's no picnic, there's little to stop > >> anyone from doing it, or at least trying it. On the other hand, getting > >> Java on the iPhone requires perhaps less engineering (if there's a JVM for > >> the iPhone CPU), but it requires Apple's consent, which may or may not be > >> forthcoming. > > >> -- > >> Mark Murphy (a Commons Guy) > >>http://commonsware.com > >> _The Busy Coder's Guide to Android Development_ -- Available Now! > > > -- > > take care, > > Muthu Ramadoss. > > >http://cookingcapsules.com- nourish your droid. > >http://mobeegal.in- find stuff closer. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
