May 29 AT 2:47 AM Taylor Wimberly 25 Comments

Wave Goodbye To Native Android Apps From Google?

Today Google announced Wave – a new tool to organize all your online communications.  During the demonstration, they showed off a mobile version running in the browser on Android and iPhone.  I was absolutely blown away by the potential of Wave, but I was curious if we would see a native app on our phones.

Shortly after the keynote, there was a press conference and we were allowed to ask questions to the Wave team, Vic Gundotra, and Sergey Brin.  Since I’m an Android fanatic, I had to ask about the possibility of seeing an official native app for Android or iPhone.  To summarize their response, “No”.

Google touted that Wave was developed entirely with the Google Web Toolkit and fully utilized HTML5.  They envision the web as the platform of the future and the browser is becoming more like the operating system.  By creating web only apps, they can bypass all the time it takes to write native code for Android and iPhone.  This also means that all their new web apps will be readily available on Palm’s WebOS.

Another advantage of focusing on mobile browser apps is choice for the end user.  Several carriers have expressed interest in releasing Android phones that are free of Google.  If all the apps are available on the web, the user can still access their favorite Google services directly from the browser.  Carriers could always block the Google domains, but I doubt users will stand for walled gardens anymore.

So what does this mean for Android users? Will we see Google release any new native apps for Android?  I have been eagerly waiting to see native apps for Adsense, Analytics, Reader, and more.  After this week, it looks like I may be waiting a long time.  Instead of spending time on native apps for Android, Google will create mobile browser apps that work across multiple platforms.

We have already witnessed this strategy with the recent updates to mobile Gmail.  New features were first released on the mobile site, then weeks later the native app got an update.  However, the mobile browser version still offers functionality not available in the Android client.  Today’s unveiling of Wave just continues the same pattern.

So is all hope lost for native Google apps on Android?  The answer to that question lies with the community.  Either we whine to Google or we create the native apps on our own.  A quick search of the Market and you will find people doing just that.  Developers have already created Android versions of Adsense and Analytics.

Check out the official video of the Wave keynote and let us know what you think.

Taylor is the founder of Android and Me. He resides in Dallas and carries the Samsung Galaxy S 4 and HTC One as his daily devices. Ask him a question on Twitter or Google+ and he is likely to respond. | Ethics statement

    Most Tweeted This Week

  • Eric

    Is it really that important if an app is in a browser or native? All the mobile apps I use seem to work for me just fine, i.e. Google Reader, etc. As long as the app does what I need, I don’t mind if it’s a web app vs. native.

    • http://Website progician

      I would say it is necessary in a case of a semi-chat program. If I see a terribly slow application on my desktop computer, why would a vast weaker pocket computer perform well enough. I think here’s the day for creating a native/java client for wave.

  • http://zorrilla.me Gabriel A. Zorrilla

    Well, It may affect developers having to get proficient in other stuff rather than pure Java/Android.

    But honestly, if there is a way for the browser to access bar notifications, that would completely replace an online App, which is what Google is about. They have, calendar, mail, etc, already with off-line access, its kinda pointless for Google to duplicate the funcionality in Android. I see non connection intensive apps such as games, utilities, etc to be native, and online intensive, with the browser as middleware.

  • http://nitenren.blogspot.com Renarudo

    It’s mostly convenience. It’s easier for me to click on my email app than it is to go into Browser and log in.

  • http://en.wikipedia.org/wiki/Jonestown Jim Jones

    I think you’re drinking the Kool-Aid a little too soon.

    I think we all need to see how HTML5′-class implementations perform on a device like the Palm Pre.

    If the performance isn’t equal to iPhone applications then HTML5 will remain a good, but not superior, short-cut alternative to developing a cutting edge mobile OS.

    I suspect that most device manufacturers will cut their losses and head toward an HTML5 solution but if they can’t match the iPhone the consumer will recognize which platform works better.

  • http://commonsware.com/Android/ Mark Murphy

    I’ll echo some of the sentiment in the comments here.

    Google isn’t going for monopoly status with Android. It wants its apps and services and ads to be on all mobile platforms, Android included. So, sticking with a Web UI as their main avenue for wave makes sense.

    What is not clear is what sort of offline model wave will support. That’s important for mobile, since not everybody is universally connected, or has unlimited data plans. That may be where Android winds up shining, if offline mode requires hooks beyond HTML5 and therefore winds up being implemented primarily for Android, since they may lack the ability to implement said hooks for other platforms. In that case, Google wave online is equal on all platforms, but Google wave overall would be better on Android.

  • http://www.nexsoftware.net nex.Software

    Did we ever say hello to native Android apps? I mean, really? Aside from the core apps of Android 1.0, we haven’t seen anything new. In the sessions at I/O, I don’t think we can count on the Browser to be a be-all-end-all solution for everything. Sure the capabilities are growing and web-based apps are getting more powerful but I don’t think they will replace the need for “native” apps. We may not, however, see much more from Google itself outside of the core of Android though.

  • Roy

    I still hope for a native app for wave and google docs. Call me crazy, but I want it. I can wait though. If wave gets picked up by a lot of people, then it will thrive. If it’s only made useful for android users, then it’s not going to make it.

    I have never liked email so I am dying to see this work. However, I still think an application like this will work beter as a native app. The browser has the tendency to freeze the homescreen when returning, doesn’t have notfications (yet), has no menu functionality (besides the browser)…

    Could you post a link as to where they said it wasn’t going to be done?

    • http://www.nexsoftware.net nEx.Software

      I think it was asked/answered in a press conference or one of the sessions at I/O. I’m not sure that there is anything official (in writing) that it won’t happen, but it certainly seems likely.

    • http://clarklab.net Clark Wimberly

      I don’t know if that information is online anywhere, but Taylor asked “Do you have any plans to release a native Android or iPhone app for Wave?” and the answer was just a flat out “No”

      And that was during the official press briefing with Lars, Jens, and Sergey.

      I think the overall goal is to make the mobile web so good that we don’t need native apps. Wouldn’t it be great if all apps just worked on all devices?

  • http://friendfeed.com/derlinzer Ralph

    I agree with Mark: As long as browser apps can’t/use notifications and can’t/don’t integrate with other apps (mail to, send with, call, etc…) i don’t see browser apps as an alternative to native apps.

    Next thing is the browser itself: To be used for apps, it has to get a lot – and i mean a lot – faster to come even close to running native apps.

    Maybe i’m seeing things too negative or too narrow. Maybe it’s not about opening a browser, opening Gmail, etc… Maybe future apps just use the browser engine for rendering and will use certain system hooks.

  • Pingback: Google dropping native application support for Android? | Fommy - Wireless Tech News and Reviews()

  • Pingback: Android and Me()

  • Pingback: Mobile Tweaks | #AskAndy – Your Android Questions Answered Volume 7()

  • ipauldev

    There’s nothing stopping us from creating our own native app. Start here: http://code.google.com/p/iwaveclient/

  • Pingback: Android and Chrome will likely converge over time says Google founder – Android and Me()

  • Pingback: Android and Me()

  • Pingback: Are mobile apps here to stay? « brelson.com()

  • Pingback: Android and Me()

  • Pingback: Android and Me()

  • http://www.android-tr.com saane

    How about google buzz?

  • Pingback: Goodbye old Browser, Chrome to become the standard browser on Android 4.0 and above – Android and Me()

  • Pingback: Goodbye old Browser, Chrome to become the standard browser on Android 4.0 and above | Gadgets Tech Tips News()

  • Pingback: Goodbye old Browser, Chrome to become the standard browser on Android 4.0 and above | Gadgets City()

  • Pingback: Android Wave | Sladescross's Blog()

  1. EricGuest 6 years ago

    Is it really that important if an app is in a browser or native? All the mobile apps I use seem to work for me just fine, i.e. Google Reader, etc. As long as the app does what I need, I don’t mind if it’s a web app vs. native.

    • progicianGuest 5 years ago

      I would say it is necessary in a case of a semi-chat program. If I see a terribly slow application on my desktop computer, why would a vast weaker pocket computer perform well enough. I think here’s the day for creating a native/java client for wave.

  2. Gabriel A. ZorrillaGuest 6 years ago

    Well, It may affect developers having to get proficient in other stuff rather than pure Java/Android.

    But honestly, if there is a way for the browser to access bar notifications, that would completely replace an online App, which is what Google is about. They have, calendar, mail, etc, already with off-line access, its kinda pointless for Google to duplicate the funcionality in Android. I see non connection intensive apps such as games, utilities, etc to be native, and online intensive, with the browser as middleware.

  3. RenarudoGuest 6 years ago

    It’s mostly convenience. It’s easier for me to click on my email app than it is to go into Browser and log in.

  4. Jim JonesGuest 6 years ago

    I think you’re drinking the Kool-Aid a little too soon.

    I think we all need to see how HTML5′-class implementations perform on a device like the Palm Pre.

    If the performance isn’t equal to iPhone applications then HTML5 will remain a good, but not superior, short-cut alternative to developing a cutting edge mobile OS.

    I suspect that most device manufacturers will cut their losses and head toward an HTML5 solution but if they can’t match the iPhone the consumer will recognize which platform works better.

  5. Mark MurphyGuest 6 years ago

    I’ll echo some of the sentiment in the comments here.

    Google isn’t going for monopoly status with Android. It wants its apps and services and ads to be on all mobile platforms, Android included. So, sticking with a Web UI as their main avenue for wave makes sense.

    What is not clear is what sort of offline model wave will support. That’s important for mobile, since not everybody is universally connected, or has unlimited data plans. That may be where Android winds up shining, if offline mode requires hooks beyond HTML5 and therefore winds up being implemented primarily for Android, since they may lack the ability to implement said hooks for other platforms. In that case, Google wave online is equal on all platforms, but Google wave overall would be better on Android.

  6. nex.SoftwareGuest 6 years ago

    Did we ever say hello to native Android apps? I mean, really? Aside from the core apps of Android 1.0, we haven’t seen anything new. In the sessions at I/O, I don’t think we can count on the Browser to be a be-all-end-all solution for everything. Sure the capabilities are growing and web-based apps are getting more powerful but I don’t think they will replace the need for “native” apps. We may not, however, see much more from Google itself outside of the core of Android though.

  7. RoyGuest 6 years ago

    I still hope for a native app for wave and google docs. Call me crazy, but I want it. I can wait though. If wave gets picked up by a lot of people, then it will thrive. If it’s only made useful for android users, then it’s not going to make it.

    I have never liked email so I am dying to see this work. However, I still think an application like this will work beter as a native app. The browser has the tendency to freeze the homescreen when returning, doesn’t have notfications (yet), has no menu functionality (besides the browser)…

    Could you post a link as to where they said it wasn’t going to be done?

    • nEx.SoftwareGuest 6 years ago

      I think it was asked/answered in a press conference or one of the sessions at I/O. I’m not sure that there is anything official (in writing) that it won’t happen, but it certainly seems likely.

    • I don’t know if that information is online anywhere, but Taylor asked “Do you have any plans to release a native Android or iPhone app for Wave?” and the answer was just a flat out “No”

      And that was during the official press briefing with Lars, Jens, and Sergey.

      I think the overall goal is to make the mobile web so good that we don’t need native apps. Wouldn’t it be great if all apps just worked on all devices?

  8. RalphGuest 6 years ago

    I agree with Mark: As long as browser apps can’t/use notifications and can’t/don’t integrate with other apps (mail to, send with, call, etc…) i don’t see browser apps as an alternative to native apps.

    Next thing is the browser itself: To be used for apps, it has to get a lot – and i mean a lot – faster to come even close to running native apps.

    Maybe i’m seeing things too negative or too narrow. Maybe it’s not about opening a browser, opening Gmail, etc… Maybe future apps just use the browser engine for rendering and will use certain system hooks.

  9. Google dropping native application support for Android? | Fommy - Wireless Tech News and ReviewsGuest 6 years ago

    [...] their own platform as well as the iPhone, and they (being Taylor Wimberly from androidandme) was greeted with a “No.” Not only was the question an “if”, they basically said there was no possibility, a [...]

  10. Android and MeGuest 6 years ago

    [...] Many of the native Android apps are lacking in features when compared to their mobile web versions.  This is a pattern that is likely to continue.  As we mentioned last month, Google has chosen to target the browser for new services instead of coding native Android apps. [...]

  11. Mobile Tweaks | #AskAndy – Your Android Questions Answered Volume 7Guest 6 years ago

    [...] Many of the native Android apps are lacking in features when compared to their mobile web versions.  This is a pattern that is likely to continue.  As we mentioned last month, Google has chosen to target the browser for new services instead of coding native Android apps. [...]

  12. ipauldevGuest 6 years ago

    There’s nothing stopping us from creating our own native app. Start here: http://code.google.com/p/iwaveclient/

  13. Android and Chrome will likely converge over time says Google founder – Android and MeGuest 6 years ago

    [...] I guess we could have seen this coming based on Google’s comments from the last Google I/O. Google has expressed a desire to developer web applications powered by HTML5 and wants to move away from native apps. [...]

  14. Android and MeGuest 5 years ago

    [...] improving all their mobile apps. This continues their trend of focusing on web apps while slowly moving away from native Android apps. First up, Google Search results for movies got a face lift. The new movie listings page now [...]

  15. Are mobile apps here to stay? « brelson.comGuest 5 years ago

    [...] adamant that this was not the case and that mobile apps were here to stay. He cited Google’s increasing preference for mobile browser apps over native apps, even for its own Android platform, and more or less said that they were wrong on this one. Mobile [...]

  16. Android and MeGuest 5 years ago

    [...] have been questioning if native Android apps from Google were a thing of the past, but it looks like the company is willing to give its services more mobile love now that they will [...]

  17. Android and MeGuest 5 years ago

    [...] adamant that this was not the case and that mobile apps were here to stay. He felt that Google’s increasing preference for mobile browser apps over native apps was misguided and that Google were wrong on this one. Mobile browsers were so far from rivaling the [...]

  18. saaneGuest 5 years ago

    How about google buzz?

  19. Goodbye old Browser, Chrome to become the standard browser on Android 4.0 and above – Android and MeGuest 3 years ago

    [...] was not advanced enough to achieve that goal. Back in 2009, we thought that Google would abandon native Android apps in favor of web apps, but that obviously didn’t [...]

  20. Goodbye old Browser, Chrome to become the standard browser on Android 4.0 and above | Gadgets Tech Tips NewsGuest 3 years ago

    [...] was not advanced enough to achieve that goal. Back in 2009, we thought that Google would abandon native Android apps in favor of web apps, but that obviously didn’t [...]

  21. Goodbye old Browser, Chrome to become the standard browser on Android 4.0 and above | Gadgets CityGuest 3 years ago

    [...] was not advanced enough to achieve that goal. Back in 2009, we thought that Google would abandon native Android apps in favor of web apps, but that obviously didn’t [...]