Selecting Pocket Casts

I am a long time listener to podcasts. Originally, I listened to podcasts using my iPod Touch, but the iPod then didn’t provide a way to make a playlist of podcasts so once an episode completed you had to manually start the next episode, which was not very safe while driving.

  • I started by listening to the Daily Source Code produced by Adam Curry but today I listen mostly to shows on the TWiT network.

Shortly after I got my first Android phone I bought DoggCatcher, which I think may have been one of the very first podcasting apps for Android. While I was happy using DoggCatcher, when Google Listen became available I was drawn to it by the ability to manage your podcast subscription lists using Google Reader.

I also liked how Listen automatically put new episodes at the top of the playlist making it easy for me to quickly find the latest and greatest episodes of the podcasts I follow. Unfortunately, Google retired Listen, but it didn’t “disappear” from my Galaxy Nexus, so I kept using it until the Nexus’ untimely demise.

  • Pocket Casts catalog

With my Galaxy Nexus no longer functioning, I had to find a replacement for Google Listen to install on the Samsung Galaxy S2 provided by my employer, so I went back to DoggCatcher. DoggCatcher has improved significantly since I used it last and I am particularly happy with its Android lock screen controls.

  • With Google retiring Listen, it is no longer easy to install it on a new Android phone, although I believe that you can manually find and install it from your apps list in Google Play.

An increase in using my work provided smartphone during my commutes has forced me to either pick the Galaxy S or the HTC One for listening to all podcasts, or find a way to sync what I listen to between the two phones. DoggCatcher has a cloud synchronization function that is in development but is not available to me now. I learned that Pocket Casts has a working sync function, and with a $25 Google Play store credit, I decided to go ahead and buy it to check out. In another article I will write about how Pocket Casts meets my criteria for podcast apps.

Posted in How | Leave a comment

Painted Into A Corner

Innovation

The highly anticipated iOS announcement at this year’s Apple WWDC conference confirmed the updating of the iOS user interface. Along with showing a refreshed UI, Apple announced additional features of iOS that frankly put it on par with Android and Windows Phone.

While one can debate the merits of iOS looking more like Android, or adding features first introduced by webOS, I think doing so misses the bigger question, how much innovation is left in smartphones?

Apple did not create the first smartphone, depending on who you ask that recognition goes to either Nokia, Palm, or Microsoft. Apple did make the first successful smartphone, and the innovations associated with the iPhone include the on-screen keyboard, a touchscreen that doesn’t require a stylus, and an application store.

The problem is that all of the innovations that Apple added to the smartphone market are confined to the phone, and if you are confined to only the phone there is only so much innovation that can made from it. Consequently, further innovation in the smartphone market must come from areas outside the bounds of the phone itself, and this I think is Apple’s biggest risk.

As evidence I cite Siri vs. Google Now. After Apple aquired Siri and announced it as a core feature of iOS, it was hailed as the next big innovation. Truth is, however, that so far Siri has been demoed better than in actual use. After the initial excitement wore of, most people stopped using Siri, and I doubt adding additional voices to Siri and support for Twitter is the trick for making Siri successful.

In my opinion, the problem is that Apple sees natural language interaction with Siri to be its core feature, and that stands in contrast to Google who sees the primary purpose of Google Now as providing answers to user’s questions, links to Internet sites that may contain answers to user’s questions, and perhaps most importantly, anticipating and presenting information it thinks users will find useful before users even ask for it.

In short, Siri is attempting to be an evolution of the user interface while Google Now, and the underlying Google Voice Search, is an evolution of Internet search. Siri’s weaknesses are exposed as soon as it needs to go beyond the smartphone to Internet servers to which it has either insufficient connectivity or server horsepower to quickly respond to user queries.

Siri’s weaknesses are the result of a company who’s history is in great UI and product design but not in web services. In contrast, Google Now’s strengths are a result of a company with a strong history in developing web services and who has experience with using the power of the entire Internet to answer user questions and provide them information.

As self contained devices, there is little innovation left for smartphones, but as an entry point to the power of the Internet, innovations that include smartphones are only limited by our ability to develop new web services. In light of this premise, which company do you think is likely to provide future innovations, the best product company in the world or the best web services company in the world?

Posted in Experiences | Leave a comment

Where Is Google Taking Android?

JR Raphael says that Google is deconstructing Android, and that is awesome, but what does that mean?

Google has been slowly separating the Google Experience from Android

When Google first launched Android, it included core Google apps like Maps, Gmail, and the Android Market. The bundle of Android and the core apps became known as the Google phone, and the phones that had the entire bundle had the “With Google” logo located on the back.

T-Mobile G1

The core parts of Android are open source, which enables Amazon and Barnes & Noble to use it to make their own tablets without paying Google for Android, but that doesn’t include the core Google apps for which manufacturers pay a fee to be able to include. While most Android device manufacturers pay the fee to include Google Play and the other core applications, they are able to pick and chose what to include and what to develop to create their own user experience.

The combination of different user experiences, different availability dates of upgrades to Android, and the different versions of Android included in new phones has been labeled by the press as “Android fragmentation.” The consequence of fragmentation is many different versions of Android being available, users not being able to upgrade their phones to the most current version of Android, and developers having to test their apps on too many versions of Android.

Google determined that the real issue of Android fragmentation is that the parts of Android that users see and use is not being kept current by the manufacturers and that users have no way to upgrade those parts on their own. Most people don’t care if the Android kernel on their phone is not current, but they do care if the version of Maps is not current.

Google also realized they couldn’t get hardware manufacturers nor the carriers to release upgrades fast enough.

So, their solution is to separate the apps that make up the Google Experience from Android and distribute updates to them via the Play store, which just about every device other than Amazon’s has installed. Consequently, users now get updates to the parts of their Android phone they care the most about as soon as Google releases them.

What To Watch For

Some key components of the Google Experience remain bundled with Android, and in order for the fragmentation issue to be completely resolved they will also need to be separated. The key components to look at are the Launcher and the Play store.

The Launcher

The Launcher is Android’s primary user interface and includes the home screens, support of widgets on the home screens, and the app drawer. HTC Sense and Samsung’s Touchwiz are basically alternatives to the Launcher that Google provides with Android. Several alternative Launchers are also available in the Play store.

If Google releases the stock Android launcher as a separate app in the Play store, and perhaps calls it Google Home, that means if you own an HTC One you could make it function as stock Android phone. Another potential result of Google distributing the Launcher via the Play store is that they would no longer need the Nexus devices because users would be able to convert any phone running the Android kernel in to a “stock” Android phone.

The Play Store

Key to Google’s plan of addressing fragmentation is their control over the Play store, it allows them to make their apps available and push updates to any phone that has Play. If handset manufacturers chose to prevent users from replacing their user experience, they would have to remove Play from their phones AND prevent users from installing apps from any other source.

To not include Play on their phone, manufacturers would have to provide their own app store or partner with someone else like Amazon. If manufacturers started building phones with their own store and apps, Google could be forced to make Play a separate app like their other core apps and prevent manufactures from being able to block the ability to install apps from third parties.

So far, handset manufacturers have not taken steps to prevent users from replacing their user experience with another that is available in the Play store. For example, today you can replace HTC Sense with Nova Launcher. The worry is whether the Android handset manufacturers will start a war to preserve their user experience at the expense of users. Samsung has already their own app store and has been working on their own mobile operating system.

  • I’ve recently been shocked to realize that I actually prefer using HTC Sense on the HTC One rather than stock Android, and therefore I don’t think I would actually install the Android launcher on my phone if it were available. The main reason why I prefer it is that I have come to really like Blinkfeed.

Fewer Android Upgrades

Finally, another result of Google’s apparent fragmentation plan is that they can slow down the frequency of updates to Android. I think we have already seen this in the fact that Google did not announce Key Lime Pie during the Google I/O conference.

Fewer Android upgrades will increase the likelihood that the majority of phones will have the same version of the operating system, and that will be appealing to developers and corporate customers. Developers and corporate customers would prefer to see less frequent updates to Android as each update requires a lengthy, and therefore costly, testing process. I would not be surprised if we did not see a major upgrade to Android until next year.

The Strategy Is Working!

In my opinion, the strategy is working to the benefit of everyone. Separating the core apps actually makes it easier for Google to quickly release updates because the releases don’t depend on fewer teams within Google, and don’t need to go through the manufacturer/carrier blockade.

Users see more frequent updates, and with that feel better about the investment they made in the smartphone they purchased. To the average user, it feels that Android is “newer” than iOS just simply because they seem to get a new version of Gmail or Maps, or other Google apps much more frequently.

  • iPhone users also benefit too because now Google releases iOS versions of their apps as frequently as Android versions.

Developers, manufacturers, corporate customers, and carriers are happier because they don’t feel stuck on the constant treadmill of having to test new changes to Android. However, I do understand how manufacturers and carriers may be slightly dis-satisfied because the result could be users not buying new phones as frequently.

So, when do you think we will see the Google Launcher?

Posted in Opinion | 1 Comment

Jawbone UP Time Zone Issue

I’ve been wearing the Jawbone UP wrist band since January after receiving one as a Christmas present. The UP tracks my activity and sleep and is an important part of my goal to increase my activity this year.

Jawbone UP Band

To configure the band and collect data from it you need to connect it to an iOS or Android smartphone and sync it with the UP app. The date and time is set on the UP using the current date and time settings of the smartphone.

Last week as I traveled around Lake Michigan I was in the central time zone and my HTC One automatically changed time zones. After I synced the UP with the HTC One the UP changed time zones, so the times shown in the app were on central time.

Upon returning home the HTC One changed back to eastern time, but despite this the UP continues to be on central time, and there is no setting in the UP app to change the wrist band to a different time or time zone.

  • I should point out that the times I see are in the app as there is no real way to directly see the current data and time on the band.

After searching the Jawbone support site, it appears other people are having the same problem and Jawbone has not provided a clear solution. Recommended solutions include:

    • Uninstalling the app and then re-installing it.
    • Clear the app data on Android phones.

When I first received the UP they did not have an Android app and therefore I installed the UP App on my iPad and synced with it. Later, after Jawbone released the UP Android app, I started syncing the wrist band with both my iPad and HTC One.

This morning I noticed that my iPad was not set to automatically change time zones. I configured the iPad to automatically change time zones, confirmed it was on the right time and time zone, and then synced the UP with the iPad. It appears that the UP is now using the eastern time, or at least the data in the app is on eastern time.

I don’t know if changing the time zone on the iPad did the trick, or just syncing with the iPad did the trick. If it is just the sync that may be due to the fact that I first setup the UP using my iPad and as far as it was concerned the HTC One is just a secondary device.

Posted in Experiences | Leave a comment

What I Learned On The Lake Michigan 2013 Tour

As I last wrote, last week I traveled around Lake Michigan, visiting family and friends, and I packed a fair amount of tech gear for the trip. Now that I am back in the friendly confines of my home, I thought I would write a quick follow up highlighting what I learned on the trip.

ASUS VivaTab RT Requires Its Power Adapter

I packed the ASUS VivaTab RT to show it off to some friends, but unfortunately that did not work because the battery died before I could even take it out of the bag. I did pack the USB charger cable, but it does not work with the Moshi Rewind, nor any of the other USB power adapters I had with me.

Apparently you must use the adapter that came with the VivaTab in order for it to charge. What a disappointment as I expected to be able to charge the VivaTab with the Moshi Rewind given that it charges an iPad. I would understand if it took longer to charge the VivaTab with other power adapters, but at least it should still charge.

Google Doesn’t Play With The HTC Media Link HD

Hotel geeking

I did successfully connect the HTC Media Link HD to the hotel television set that had an HDMI port, and I was able to connect my HTC One to the Media Link over both the hotel’s WiFI and via the point-to-point WiFi connection. The hotel’s WiFi access is not really designed for facilitating this type of connection, and I did experience some lag in the video quality when streaming either Netflix or the MLB At Bat app.

To fully test the point to point connection between the HTC One and the Media Link I needed to download a movie to my phone. Google Play is the best source for such movies because it enables you to download movie rentals. Unfortunately, Google has placed DRM on their movie rentals that prevents one from playing the movie if the Android device is connected to an external display. No matter whether the movie was downloaded or streaming, it would not play on the Media Link, although it would play just fine on the phone.

My Phone Is My Camera

The Panasonic Lumix DMC-FZ7 I packed never left the bag because I took all of my pictures with my HTC One. In this case, it was really a matter of the phone being with me no matter where I went and forgetting to take the camera with me.

Posted in Experiences | Leave a comment