Opera has posted about their experiences in porting the browser on their blog here.  They relied on MicroEmulator’s implementation of JavaME, and discuss the challenges in working with the changing API.  To try the current Opera Mobile for Android, click here to download the APK.

Source: Opera Mini for Android [labs.opera.com]

Out of all of the projects being announced for Android (or for the iPhone SDK), geotagging photos, notes, and documents seems to be the big feature.  While it certainly is the largest advancement that the new breed of mobile phones has to offer, I am curious how large the space will be for startups to jump in and fulfill users geotagging needs.  I look forward to my expectations being blown away when the phones are released later this year.

Source: Tutorial 1:  Transparent Panel (Linear Layout) on MapView (Google Map) [blog.pokerjourney.com]

To download, visit the SDK homepage.

At first glance, the new UI is a welcome update, although the forums still rumble of a lack of chance in telephony and overall innovation.   As developers release tutorials and sample code for the new UI, we’ll link to them here, as well as to information about our own reader’s projects.

Source: Android SDK M5-rc14 Now Available [android-developers.blogspot.com]

New UI pics displayed at Mobile World Congress by NEC are of the new Android UI which were spoken about by Google’s Dan Morrill at the Google Android Workshop in Munich, Germany at the end of January. The new UI will be included in the next SDK update.

Reuters and Engadget both feature photo galleries featuring the new UI.

Google spokesman Barry Schnitt explained the event to the AFP.  “What is happening with Android today is that we are seeing a number of technology companies demonstrating how Android will operate on their technology”

All of the major tech blogs are there to cover the event today.  Engadget is showing off an amazing gallery of photos, while TechCrunch has a limited video of the Android interface, which will be nothing but familiar to those working with the SDK.

If anything, the event shows that the big players are working with Android, that progress is being made, and that hopefully, the internet will start to become very accessible to average people in 2009.  By making the mobile internet easier to use, and more accessible, we will likely find ourselves taking advantage of the increased connectivity for communication, commerce, and information at a level that’s hard to imagine, even for a culture that in 10 short years has found themselves increasingly connected to the internet.  The potential is similar to the adoption of PC computers in the home.  The open source Android platform will make it easier and cheaper for handset manufacturers to distribute and sell a more internet-able phone.

In fact, with Google’s play into the 700Mhz spectrum, mobile computing may finally become affordable, and many may see cell phones as a cheaper alternative to owning computers.

Source:  Google’s Android software debuts in Barcelona [AFP]

The progress is good news for developers, and for Google who expects handhelds running Android to be released in the second quarter of 2008. As more progress is made, we draw nearer to the Android Developer Challenge deadline of April 14th. The progress is encouraging for Android developers who look forward to releasing their apps and capturing part of the Android market, which has recently been estimated to start at 2% by Strategy Analytics.

With the iPhone set to release their SDK this month, Android faces an initial setback. While their SDK has been first to market, allowing developers to pre-develop their applications, Apple will allow developers to get their applications live first, and many developers may choose to support iPhone apps over Android apps, at least initially. This is similar to Facebook launching their app platform first, and other social networks struggling to attract developers with unique applications. What platform will you be developing for in March?

Source: ARM Google phone platform demo Monday: source [reuters.com]

A La Mobile says the “demonstration proves that Android can deliver on its promise of making it easier for consumers to get access to all sorts of applications.”

With its’ modular based operating system, allowing users to choose which applications perform core functions such as the web browser, camera, phone dialer and more - application suites such as these will compete heavily for market share of the Android “desktop”. While most Android users will likely opt in for open source (free) applications to meet their needs, it will be interesting to see what suites each handheld manufacturer chooses to distribute and how each handset’s software will differ from the rest, and whether any of them will develop their own, alone or in cooperation with the wireless networks.

Source: Introducing the first Android prototype [usatoday.com]

The specs for the GW4

• TI OMAP 1710 chipset
• 216-MHz processor
• 64 MB of program memory
• 802.11g Wi-Fi
• built-in SIP VOIP client for Internet calling
• 2.5-inch, 320×240 touch screen
• 2-megapixel camera

The software features programs for Outlook syncing, IM, PDF reading and Opera as a web browser - but will obviously be better served and replaced by Android apps and the Android OS. A future version of this phone is promised later this year

Source: Winstron Shows Google Android Phone [pcmag.com]

db40 describes developers need for their software on the Android platform

Although Java programmers are delighted with Android’s full object oriented platform they are frustrated by its bundling with a relational database, requiring cumbersome plumbing between objects and tables. db4o fills the gap by providing a fast and secure, native Java object database that makes storing objects and sharing of data between applications simple and easy.

db4objects goes on to describe uses for their software in development, especially in contrast to Android’s built in SQLLite relational database system. They describe a scenario in gaming where a user may want to freeze their game state so that they can resume it for later play.

Already, db4o has redeveloped 2 previously released Android applications which have been rewritten to work with db40. Android Password Manager, originally written by Steve Osborne and available here. Also, MapMe, based on original code for BrowseMap by and first written about at AndroidNotes here.

Both projects offer code samples for how they repurposed the applications to use db40, and if more tutorials become available we will list them here.

Source: db4objects Announces db4o Database as Android Ready [db4o.com]