Global Geek News Blog The home of more Global Geek News insight and opinions

4Aug/091

For Android to thrive, Google must do more

For months, I have been toying around with the Android SDK.  There are a number of reasons that I have decided to being creating Android applications that range from the potential money I could make to the fact that it is an open source OS and I don't have the money or time to invest in a Mac and learning Obj-C just so I can make iPhone apps.  Along the way, I have come to realize just why android isn't an iPhone killer or at least not at this stage in the game and that reason is Google.

I will admit that for the most part, I am a big Google fan (not a fanboy), I believe that they aren't doing what they could be to really help their products, specifically, Android.  As I am sure you are aware by this point, Android is Google's mobile operating system.  While it certainly has its its drawbacks, I am sticking to my belief that in the end, it will wipe the floor with the iPhone OS primarily because it is open and designed to work on many different phones.  There are supposed to be at least 20 android phones available by the end of this year alone (the main reason I think it will eventually beat the iPhone).  Unfortunately, the biggest obstacle to achieving this goal is android's creators, Google.

There are a couple of big obstacles that Google is creating that aren't making things better for them.  The main obstacle is applications.  There are some amazing applications for android that are far and above many iPhone applications but there is a big problem, there aren't very many of them.  Last I heard, the iPhone had over 50,000 apps and growing rapidly.  How many apps does Android have?  The last I heard was around 5000.  Unfortunately, I believe that is Google's fault.  Why is that Google's fault?  One word: documentation.

In my months of playing with the Android SDK, I have discovered the documentation in many places are terrible!  In many places, there are examples using code that has long since been removed from the SDK, other lines of code that just don't work and even some that are not necessary.  This is especially true if you want to do anything with multimedia.  Want to record audio?  You are in for many hours of headaches if you are going by the examples in the android dev guide (trust me on this).  The bottom line is that if Google expects to have more applications and be a real competitor for the iPhone, it needs to do all it can for developers and that includes keeping documentation up to date.

The one other big issues I have is with advertising.  It wasn't until recently that Google finally announced the ability to put ads in mobile applications and even that is reserved for a select few that meet the various requirements including 100,000 impressions.  Having such a small group of people able to take advantage of it is bad, especially for those that want ad supported applications so they can give away their applications.  Free applications attract far more customers than paid ones, but developers still need to make money for their time and effort.  Without advertising, this won't happen like it should.  Considering the fact that Google is in the ad business, you would think that they would have had this out and ready to go the second android launched.  Clearly, Google lacks focus and dedication to Android.

If Google became truly focused and dedicated to Android, I think that within a year, it could be ahead of the iPhone, but until that happens, the only advantage they have is the ability to put their OS on many phones.  Wake up Google!

18Nov/080

Has Facebook Shot Itself in the Foot with the Verified Apps program?

Greetings Readers!

Yesterday, Facebook announced their new Verified App program. For an app to qualify as to be a Verified App, it must be trustworthy.  It must be secure, respectful, and transparent.  Oh, and you must also pay $375.

What does the app get for this high price?  Apps that get the Verified designation will be given a special badge to place on the application, designation on the application directory, plus a few other bonuses like advertising credits and easier rules on how many notifications, emails and invitations they can send out to users.  Even though developers get all of this great stuff, Facebook only expects about 10% of its current 48,000 apps to qualify.

The real question is whether its worth it for developers to pay such a high price to become a Verified App?  I really don't think it is.  While it may be just a drop in the bucket for bigger companies that have Facebook apps and might seem worth it to show their customers that their app is trustworthy, I really don't see any point in it.  If Facebook users have been getting by without that trustworthy guarantee or even caring about the applications they use enough to look into the security, I don't think that the majority of Facebook users will care of the applications they use are verified.  Most probably won't even know what it means to be a Verified App other than the fact that it stands out from other applications that don't have it.  If people really cared about how trustworthy the apps are, they would take the time to read the privacy statements and terms of use for each individual app that they use.

If the users aren't demanding an application be verified, then the developers shouldn't bother with the program.  If they users don't care about whether the app is verified, what incentive is there for developers to make their apps verified and pay $375.  Given the current state of the economy and online advertising, most people with simple apps can't afford that kind of price and it would take a long time to make enough money to cover the expense.  Unless the developer is a large company, it really isn't worth it to pay that kind of price.  I don't know any other open platforms that charge such a fee for anything, rather-less to just sport some badge of trust.

Facebook can certainly make some money off of this new program, but I don't think it is worth it.  Because of the large money amount involved in getting this badge, I believe it will alienate more developers than will embrace it.  When you have small developers who make applications for fun, they often do it because it is easy and cheap.  The less of a barrier to entry there is, the more attractive it becomes to smaller developers.  By creating such a program that insinuates that they have an application that isn't trusted because they don't have the money to get the Verified App badge, is essentially slapping the smaller developers in the face.  Considering how big apps have become to the Facebook social network, snubbing the smaller developers is not a good move by Facebook.  Insulting developers with high fees is not the way to make friends or grow the database of applications.

By Facebook turning its back on the smaller developer and basically saying they aren't big enough to matter, Facebook has shot themselves in the foot.  While the idea might give the Facebook users some piece of mind, it shouldn't come at the expense of the developers.  To create a sucessful platform, you must be able to balance the users desire for trust and security while keeping the barrier of entry to developers as low as possible.  If Facebook wants true sucess, they must be willing to do everything they can to maintain this balance, but they are already off to a bad start.  Hopefully they will see the error in their ways and make the appropriate changes to their program.

Follow me on Twitter!

-Jeremy "pcnerd37" Bray