I don't agree that changing the in call screen/incoming call screen/ outgoing call screen should be only available to handset manufacturers/ operators. A phone could do SO much more when applications could somehow hook into these screens (or even control the voice streams).
Imagine an application that could show the name of an unknown caller based on data gathered from the Internet. Or an application that displays additional call information while the call is in progress (eg call length/cost/quality/voice equalizer). Or an application that let's you choose between a normal call or a VoIP call when you press the green dial button when selecting a contact from the "native" phone book. Or an application that can change the actual voice stream that is transmitted - so you could add effects such as high/low pitch etc to your outgoing call. There are many more fun/useful applications that could benefit from this openness of the OS. Of course there are security concerns but still.. For a regular user a call would work like a call and it would be sort of like a call but for "advanced" users who download these applications (and click on thousands of security warnings when installing the app) the phone would be so much more than the phones that are on the market today. Just my 2 cents.. On Sep 17, 6:47 pm, "Mark Murphy" <[EMAIL PROTECTED]> wrote: > > I think the idea is that certain key functions of the phone - calling, > > and going to the home screen - usurp other functions. All non built-in > > key functions, e.g. applications, are still equal, but yes a few key > > functions have a higher priority > > I suspect there will be two tiers of development for Android. > > At the level of the SDK, you're probably correct -- not each and every > phone function can be replaced or hooked into, in part for security > reasons. > > If you're willing to roll your own firmware, though, you'll probably be > able to do whatever you want. So if you're creating your own phone, and > you want to create a different dialer or in-call display than what stock > Android comes with, you can probably do it. > > Leastways, that's how I'm reading the various tea leaves. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.2 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
