The T-Mobile G1 manual at the URL http://support.t-mobile.com/knowbase/root/public/tm30235.pdf
reads > Install contents > 1. On the Home screen, touch the Application button. > 2. Touch Market. > 3. Navigate to and select the item you want to install. > The Item details screen appears. Read more about the item on this screen, > including its overall rating and comments by users. If you scroll down to > the About the developer section, you can view more applications by this > developer or send the developer an e-mail message. > 4. Touch Install (if free) or Buy. > - After selecting Install, the item will start downloading immediately. > - After selecting Buy, you may be asked to sign in to an additional > Google account. Sign in and select Purchase now if you want to proceed. > Step through the purchase screens. > > Important! If an application requires either access to any of your data or > control > of any functions on your phone, before you proceed, you will see a screen > telling > you what the application can access so you can give your permission. Be sure > to > read this carefully! Be especially cautious if an application has access to > many > functions or a significant amount of your data. Once you touch OK on this > screen, > you will be responsible for the results of using this item on your phone. > All support for Market applications is provided by the developer of that > application. The developer information is available on the detail page for > each > application. Alternative means of installation are not listed in the manual. Does this mean that website owners will not be able to let T-Mobile G1 owners install Android applications directly from their own website, and are entirely dependent on T-Mobile Market or Android Market to serve their customers? With J2ME this restriction generally does not apply, and phone owner can just install JAR program files from any website they trust. The scary outlook would imply full control to block application distribution at the discretion of T-Mobile and Google. This complete blocking ability in the critical path of third- party application deployment would not exactly match my interpretation of "open". What do other developers think? In my testing with the SDK 1.0 r1 emulator I indeed found that I could not install my own APK application file through the emulator browser, getting the error message "Install blocked. For security, your phone is set to block installation of applications not sourced in Android Market". My APK file is signed, and has the proper MIME type for downloading, and it installs without problems (also on other PCs) when using adb install myapp.apk instead of going via the emulator browser. Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to android-discuss@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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
