Sponsors

Wednesday, June 24, 2015

On-Screen or Physical/Capacitive Navigation Buttons – Which is Better?

Over the last couple of years, if you asked me which navigation button setup I preferred on a phone – on-screen or physical/capacitive – I wouldn’t have hesitated to say “on-screen for life, my brothers and sisters.” Google has fully convinced me that navigation buttons should be a part of the phone’s software, not hardware. At least, I thought they had fully convinced me. After having spent the past few months caressing a Galaxy S6, calling it the best phone you can buy, and poo-pooing most of the others, I’m now having this awkward internal debate with myself. Which setup do I actually prefer at this point?

I don’t know. 

After Google introduced us to on-screen buttons for phones with the release of Ice Cream Sandwich (don’t you dare bring up Honeycomb), I was instantly hooked. They gave you this immersive experience while using your phone that we didn’t have prior, but they also made navigating a phone so quick, because you didn’t have to physically press a button or leave your display as you reached for the bottom chin of your phone. And you could swipe up for Google Now! Damn, do I love that gesture.

But then Samsung went ahead this year and added in the best mobile fingerprint scanner and the quickest camera launching shortcut known to man in their physical home button. I now can’t put down the stupid Galaxy S6. It’s so pretty. And good. And shiny. I don’t even mind the button setup that I swore off so long ago. What is happening.

Of course, on-screen buttons have their issues, as do physical/capacitive setups. I know, because I see them listed out in the comments through never ending debates like the one I’m having right now with myself. So let’s do this – how about I list out the good and bad for each and then we try to settle this together? (Good luck.)


onscreen buttons-4

On-screen Buttons


  • Good:  They give you an immersive experience, especially now that the navigation area can be fully transparent or take on the colors of the apps you have open. Software tricks like these, when implemented correctly, really add a level of polish to a phone.
  • Good:  Buttonless is prettier. Without buttons jutting out from the front of your phone’s surface, you get a clean glass experience that to me, looks so good.
  • Good:  Gestures! That gesture to swipe up into Google now is the best, especially for those of us who use 3rd party launchers and can’t just swipe-over like you can in the Google Now Launcher. It also makes accessing ol’ Google easier than ever.
  • Good:  Flexibility on a number of levels. For one, Google is showing us with Google Now on Tap that they can enable things like long-presses in on-screen buttons that add functionality. But not only that, companies like LG have given users the opportunity to customize the arrangement and number of buttons that appear in the navigation area. While I prefer the standard Back-Home-App Switcher, I can see why someone might add a menu button or notification pulldown shortcut.
  • Good:  On-screen buttons are essentially future proof. What I mean is that as Google continues to change the look of their on-screen buttons, phones with on-screen buttons have a better chance at being current. Take the DROID Turbo as an example of why you wouldn’t want to use capacitive buttons. It was released with KitKat a few weeks before Google released Lollipop. With Lollipop, Google changed the theme of the buttons to the Playstation-ish theme you are seeing on the Moto X above. The DROID Turbo, assuming it gets Lollipop some day, will forever have pre-Lollipop buttons. And what if Google decides that Android doesn’t need an app switcher and needs a dedicated search button or something? Sorry, DROID Turbo users, you get to keep your app switcher.
  • Good:  On-screen buttons leave manufacturers the opportunity to trim up a phone’s chin or add additional features to it. Forget the LG G4 and its massive chin and instead consider that I’m referring to the Nexus 6, HTC One series, and Moto X. With the Moto X, Motorola created a chin area that is absolutely tiny, which means the overall phone size is reduced. With the Nexus 6 and One series, Motorola and HTC were able to add in secondary speakers that give you a stereo experience. If you have physical or capacitive buttons, it becomes tough to shrink the size of an area or add in extra functionality outside of a fingerprint sensor.
  • Good:  You don’t have to physically press down a button.
  • Bad:  They take up precious pixels. Your Quad HD display with on-screen buttons has less usable resolution almost all of the time than the Quad HD display on the phone with physical/capacitive buttons. That on-screen bar that houses your buttons is a part of the screen, so it’s stealing pixels. Sure, you can hide them and get all the pixels during movie or game playback, but not necessarily during your Gmail or Hangouts sessions.
  • Bad:  Few things bug me more than when I’m looking at a picture in the gallery and the on-screen buttons think they are doing me a favor by hiding. That drives me nuts because in order to leave that screen (go back or home) I have to tap the damn screen again to make the buttons appear. Ugh, extra steps.

onscreen buttons-3

Physical/Capacitive Buttons


  • Good:  With the Galaxy S6, you get that amazing quick launch camera double-tap magic. It’s the fastest way to launch a smartphone camera that we have come across and appreciate every ounce of brain-sweat that went into the idea. But physical buttons in general give you opportunities like that to customize actions that on-screen buttons may never have.
  • Good:  A physical button, at least in the case of the S6 (and iPhone), can be used as a fingerprint sensor that really adds a level of security to your phone that doesn’t impact experience. If Google wants to implement fingerprint scanning into a stock Android phone that has on-screen buttons, it’s going to have to do it somewhere else in the hardware of a phone that may not be as convenient.
  • Good:  You get all the pixels! Since your buttons aren’t on-screen, you never have to worry about them needing to hide – you always get to put to use every single pixel on that big, beautiful QHD display of yours.
  • Good:  Your buttons are always there. I mentioned how much I hate having to tap the screen in the gallery or YouTube or other areas with on-screen buttons in order to show buttons that have been hidden temporarily for a full-screen experience. With physical or capacitive buttons, your buttons are always there for the pressing.
  • Good:  With separated button and screen areas, there won’t ever be much confusion when you try to operate your phone. Look at the picture at the top of this post to understand what I mean. With the LG G4, you actually have two sets of software-powered navigation areas sitting on top of each other. The app dock there has swiping gestures built into it, just like the home button, so I often find times where I swipe one and mean to swipe the other. With the Galaxy S6’s setup, that never happens because of that hardware separation. With hardware buttons, you also should experience far fewer accidental presses.
  • Bad:  Physical buttons tend to provide a slower experience than those that are on-screen. With capacitive, the experience is largely the same, but it’s almost always easier to slide your finger over a button and have it sense a touch rather than you having to physically compress it.
  • Bad:  As I mentioned above, your physical and capacitive buttons are there for life. If Google changes the look of buttons in the next version of Android or swaps one out for something new, you don’t get to participate in the fun when we geek out about it. Related, but if companies like Samsung do this insanely stupid thing where they swap the Back and App Switcher button, you just have to deal with it.
  • Bad:  This is obviously a personal taste thing, but a physical button on the front of a phone just doesn’t let it look as clean as a phone that is buttonless. I don’t care how fancy and gold that button may be, Samsung.
  • Bad:  Look at the picture of the Galaxy S6 Active above – holy disaster.

Wow. Look at that list.

So what’s the conclusion? Well, I think I still mostly prefer on-screen buttons because of their flexibility, aesthetic they give to a phone, and their ease of use. They are also the standard that Google has tried to set for how they envision Android working, which is always something we strongly take into consideration. Not that Google is always right (Hello, Lollipop volume controls!), but this is one of those areas they seem to have gotten right.

That doesn’t mean I don’t see all sorts of value in having the button setup of a phone like the Galaxy S6. I love this phone’s camera quick launch shortcut and fingerprint sensor. I also love the dedicated area for operating my phone that often hides when I’d rather it be present on phones with on-screen buttons. I have easily been able to adapt to this phone’s button setup and don’t regret for a second calling it the best phone you can by right now.

In the end, it’s on-screen buttons for me 99 times out of 100. But should a phone like the Galaxy S6 come along with a physical/capacitive button setup done correctly, I won’t have a problem giving it some run.

On-Screen or Physical/Capacitive Navigation Buttons – Which is Better? is a post from: Droid Life



from Droid Life http://ift.tt/1J6n9Xx

Giveaway: Win Your Choice of Phones in the ‘Choose Your Own Android’ Giveaway

We have another giveaway taking place on the DL Deals Store, where you can choose which phone you want. Of course, you can’t have any phone, you will have to choose between a predetermined lineup, full of some pretty sweet devices.

Up for grabs is a Nexus 6, LG G4, G Flex 2, OnePlus 2, and Galaxy Note 4. These are some good devices, although we don’t yet know if the OnePlus 2 will be awesome. Either way, we are sure you will be happy if you end up winning.

To enter, all you need is a valid email address, as that is how you will be contacted in the case you are the winner. For more entires, you can share the contest to your social channels. Once you are all done with that, you are good to go.

The contest closes 7/8/2015 at 11:59 PDT.

Enter below and good luck.

Deal Link

Giveaway: Win Your Choice of Phones in the ‘Choose Your Own Android’ Giveaway is a post from: Droid Life



from Droid Life http://ift.tt/1Gz8wIf

This is My Android: Tim Edition (June 2015)

When you review Android devices for a living, constantly switching phones and carriers, I have found that I have a particular setup that I continuously go back to on each one, as it is what I have become familiar and comfortable with. Once the review process is over, I attempt to get rid of most signs of an OEM’s custom skin, such as TouchWiz or Sense, so the first thing I will do is load up a 3rd-party launcher.

To make that 3rd-party launcher really pop and my own, I download a few of my favorite icon packs, which is quite a few. Adding these icon packs to my device also brings a ton of different wallpapers that I can choose from, giving me plenty of options in the customization department.

In the following post, I will go over my current setup, including which phone I use as my daily driver, what launcher I use, some of my favorite wallpapers, and icon packs. Hopefully this post can help you find some apps, widgets, or wallpapers you would like to try out.

This is my current daily Android setup.


Galaxy S6 - 1

PhoneGalaxy S6

So far in 2015, I have been fortunate enough to try all of the top flagship devices from most of the manufacturers. This includes the LG G4, One M9 from HTC, Galaxy S6 Edge from Samsung, and the regular Galaxy S6. Through my experiences which each of these phones, I have decided that I would use the Galaxy S6 as my daily driver.

For me, all I really look for is a great Android experience, and the Galaxy S6 delivers that for me. Sure, the battery could use some help, but the display is gorgeous, camera is legit, and it looks incredible. To date, the Galaxy S6 may be my favorite overall Android device, though it currently holds that spot with the Moto X (2nd Gen). Side note: I cant wait to see what Motorola is cooking up for 2015.

All of the other phones I mentioned are good in some cases, but when valuing the overall experience, the Galaxy S6 from Samsung does it for me.


Nova - 1

LauncherNova Launcher

We get asked this all of the time, so allow me to settle the discussion once and for all. Kellen and I both use Nova Launcher, period. Sometimes, and very uncommonly, you may see either of us use the Google Now Launcher, but for the most part, given its ability to be highly customized, we stick to Nova Launcher.

Nova allows for the usage of 3rd-party icon packs, but not only that, settings for the home screen, app drawer, and gesture controls can be set however we like them, granting us power over how we want our phone to look and essentially operate. In the settings menu of Nova, you can tweak desktop, app drawer and dock appearance, badge counts for icons, gesture controls, and even backup or import your settings from another launcher.

If you take the look and customization of your phone seriously, you have to use Nova. And before you ask, yes, buy the Premium unlock. It’s worth every penny.

Play Link


Home screen -2

WidgetsGoogle Now, Timely, Sound Search

I have never been a big widget guy, but I do use a few that I find to be useful. Interestingly enough, people could argue that two of the three widgets I use are basically obsolete, but habit is a powerful thing. I am used to having Sound Search on my home screen, even though I could simply tap the mic button to launch Google Search and find a song that way. Something about the way Sound Search works, I just like it. It keeps my songs in order of date recognized, and to me, that’s cool.

As for having a Google Now widget on my home screen, it’s nice since Nova Launcher doesn’t allow you to swipe into Google Now, such as it does with the Google Now Launcher. I can see all of the same info, without opening up Google Now. And if I see an article I want to check out, I hit the box. It’s easy.

Now, a ton of people, and I do mean a ton, always ask what the clock widget I use is. It’s Timely. Timely was acquired by Google not too long ago, but I still like it. I enjoy the widget for the app, as it is clean and easy to read, no matter which wallpaper I have applied. It acts as my alarm clock, stopwatch, and timer. It’s just a solid clock app.

Play Links: Google | Timely | Sound Search


Iride - 3

IconsIride UI Hipster

If icon packs were a drug, I would have checked into rehab years ago, but thankfully, that isn’t the case. I can download all the icons packs and no one would even care. But as I have been switching through devices, I find myself downloading this one in particular, given its close resemblance to the stock Android icons, with a bit of color editing. For someone who enjoys vanilla, but with a pinch of something else, Iride UI Hipster is a great choice.

This pack comes with 3000+ icons in Full HD, which is good when your phone’s display is QHD. Even when you bump up the icon’s size to 130% via Nova Launcher’s “Look and Feel” menu, the icons still look crisp. One touch on the developer’s part that I appreciate is the inclusion of multiple colors for the same icon. For example, the dialer icon and camera icon have multiple color choices to choose from, really letting you decide how you want your device to appear. As an end user, I appreciate that.

Iride UI Hipster is available on Google Play for a little over $1. For access to all of these icons, plus the big pack of wallpapers to go with the set, you definitely get your money’s worth.

Play Link


This post is part of our This is My Android series. You can view Kellen’s from June right here. As time goes on, we will switch phones, and tastes in widgets and icon packs will evolve. When that happens, you will see more of these.

This is My Android: Tim Edition (June 2015) is a post from: Droid Life



from Droid Life http://ift.tt/1GqNdJx

Wednesday Poll: Who is Your Current Wireless Carrier?

It’s that time of year again, where we check-in to see which wireless carrier you are all currently signed up with.

When we asked this same question almost a year ago, 60% of you were still with Verizon, while T-Mobile had managed to attract almost 20% of the community. AT&T, Sprint, and various prepaid options made up the other 20% or so. With T-Mobile still making Uncarrier moves, AT&T attempting to copy match them offer-by-offer, and a variety of prepaid options posting insanely good monthly deals, we want to know if Verizon is still holding onto your business.

After voting, be sure to tell us why you are where you are. Is it all about coverage? Pricing? What?

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

Wednesday Poll: Who is Your Current Wireless Carrier? is a post from: Droid Life



from Droid Life http://ift.tt/1J63G9t

Google Updated Its Google Play Developer Program Policies Today, Here are the Changes

Google just pinged us to point out that they made some changes to their Google Play Developer Program Policies this morning. While we aren’t developers, we still thought everyone should be aware of the changes. So, here they are. 

  1. You will find a new Sensitive Events policy that doesn’t allow someone to make an app to capitalize on or lack reasonable sensitivity towards a natural disaster, atrocity, conflict, death, or other tragic event.
  2. Google tried to clarify the Impersonation or Deceptive Behavior policy in a fancy bulleted format.
  3. The Paid and Free Apps section (which is the payment policy) has been clarified as well.
  4. They also told us that “To ensure a secure and consistent customer support experience to our users, we’ve introduced a provision which governs the transfer of in-app virtual currencies purchased in an app.”
  5. And finally, they “specified that apps should not harm, interfere with, or improperly access application programming interfaces (APIs).”

You can read the rest of the updated program policies at the source link below.

Via:  Google Play

Google Updated Its Google Play Developer Program Policies Today, Here are the Changes is a post from: Droid Life



from Droid Life http://ift.tt/1HhyAMt

Facebook Messenger No Longer Requires a Facebook Account

Facebook Messenger no longer requires a Facebook account to sign up and use for those who reside in Canada, United States, Peru and Venezuela. Upon opening the app, all you need is a phone number, name, and picture. From there, you can chat with all of your buddies on Facebook, with you not even needing an account. Clutch. 

Of course, having a FB account benefits Messenger users quite a bit, as conversations can be carried over multiple devices and desktop computers, but if your smartphone is your main form of communication, this should serve you well.

This change is currently rolling out now, so be on the look out if it interests you.

Play Link 

Via: Facebook

Facebook Messenger No Longer Requires a Facebook Account is a post from: Droid Life



from Droid Life http://ift.tt/1KaGHLT

Google is Now Showing the Status of Your Project Fi Invite

Hey, look, my Project Fi invite status! Wait…what? Even though I was probably one of the first three people on the planet to sign-up for the service, already own a Nexus 6, am a nerd at heart who likes to test things, and live in a metro area that T-Mobile is excellent in, I’m still completely in limbo? Sure makes sense.

To the rest of you, maybe you will have better news on the newly launched status indicator for Fi. Tim’s says “3-4 weeks.” Others are seeing that as well. Me, not so much. Thanks, Google! 

Check your status here.

Cheers @chris_manuel86!

Google is Now Showing the Status of Your Project Fi Invite is a post from: Droid Life



from Droid Life http://ift.tt/1dgEDVz

Kenwood Launches DDX9902S and DDX9702S Android Auto Units, Priced at Under $1K

Back in January during CES, Kenwood introduced its DDX9902S and DDX9702S multimedia receivers, featuring CarPlay software from Apple and Android Auto from Google. These units are now shipping to retailers, according to Kenwood’s announcement this morning, with the suggested retail price set at $900-$950. 

Currently, the DDX9902S appears to be on Amazon for just $750, capable of running both Apple’s CarPlay and Google’s Android Auto. If you are looking for a solution to your car’s infotainment needs, $750 is not a bad price, plus whatever it costs to install the unit.

Personally, I have rocked a Pioneer unit in my vehicle for about a month now, so be on the look out for a full Android Auto review sometime soon, which may help you decide if you should take the leap into Google’s OS for cars.

Do you already have Android Auto installed in your vehicle? If so, tell us what you think about it.

Via: Media Wire

Kenwood Launches DDX9902S and DDX9702S Android Auto Units, Priced at Under $1K is a post from: Droid Life



from Droid Life http://ift.tt/1BMD11y

Why is Android Still the Second Platform Developers Work On?

Every year we see the same promise: this is the year that Android-first development will become a reality. At the same time we see big companies like Instagram repeatedly introduce new apps that are iOS-only. Android has been able to tout more market share than iOS for quite some time, but that doesn’t seem to have translated into app developers releasing Android apps at the same time as their iOS counterparts, much less Android-first. Over the past few weeks I’ve been talking with developers and researching why this is still the case.

Limited Resources


We see example after example of apps launching on iOS before Android from large companies like Instagram, Facebook, Nike, and even Google. Usually these companies can’t claim that they don’t have the resources or enough potential users of their product, but what about smaller independent developers?

NeuBible is a Bible app from Kory Westerhold and Aaron Martin. NeuBible entered a relatively crowded market of Bible apps on iOS, many of which are free. I don’t know if NeuBible will be a financial success, but I can say that within seconds of using the app it became my default Bible app on iOS. The one word that precisely describes my experience with the app: delightful.

NeuBible, like so many other apps, launched on iPhone first, but unlike many other apps, came with a promise to come to Android soon. Westerhold says that he and Martin had planned on releasing NeuBible for iPhone, iPad, and Android, but the massive costs of development forced them to start with iPhone only (the duo actually paid for the app’s development out of their own pockets – a testament to how passionate they are about the app!).

Westerhold was quick to point out that NeuBible didn’t launch iPhone first because he doesn’t like Android. Quite the contrary; he actually thinks NeuBible’s aesthetic fits Lollipop even more than it does iOS 8 and loves using the Nexus 6 and Moto 360. Despite his love for Android, he and Martin were hesitant to launch on Android first:

“Everything we’ve read, every number we’ve seen shows that it’s really difficult to get people to pay for apps on Android. We didn’t think we could release a paid app on Android and create something sustainable enough to fund further development.”

Westerhold isn’t the only developer concerned about the costs associated with Android development. Dave Feldman, co-founder of Emu, a third party messaging app, actually bucked the trend of iOS first and launched Emu on Android in late 2012. By April of 2014 Emu was pulled from the Play Store and launched on iOS. Developing Emu for Android hit a lot of issues working with SMS/MMS, dealing with Eclipse, and, of course, device fragmentation.

Feldman told TechCrunch, “We were finding Android in general to be a slower platform to move on. There’s more time spent dealing with fragmentation bugs. There’s more time spent dealing with testing and debugging, and we would rather spend that time building new functionality.”

According to Feldman issues they faced with fragmentation were particularly perplexing:

“On a Galaxy S4 with Samsung’s Multi-Window feature enabled, Emu’s popup windows are squished by the keyboard. This doesn’t happen on the Galaxy S4 sold by Google, without Samsung’s software modifications; or with the Multi-Window feature on the Galaxy S3. We’ve investigated, but because it relates to Samsung-specific functionality, we probably can’t fix it without direct cooperation from them.”

and…

“On some Galaxy Nexus phones, when you’re listening to Pandora and get a notification sound from Emu, Pandora’s volume drops. This doesn’t happen with other apps’ notifications, nor does it happen with streaming apps other than Pandora, nor does it happen on any other device.”

Cameron Henneke, the developer behind GQueues, had a very different experience than the folks developing Emu. GQueues was originally just a web app, but in 2013 Henneke released iOS and Android apps. While Henneke had some previous experience developing games on iOS, this was his first Android app. So of course there was a huge learning curve and massive fragmentation issues that made him curse Andy Rubin, right? It turns out Henneke managed to develop the Android version faster than the iOS version (about 870 hours to develop the Android version versus 960 hours on the iOS version).

So what can we conclude from these very disparate results? Depending on the kind of app you’re making it might be far more difficult to launch on Android, or it might actually be easier. There are enough variables between funding, the size of the team, skill set, etc. that make it impossible to say developing for iOS first makes sense for everyone, but it certainly might make sense for a small team with limited funding.

Is it really that easy to make money on the App Store?


One of the big reasons often cited for app developers going to iOS first is that the App Store is where the money is. Android users are cheap and iOS users can’t stop spending money on apps, right? That idea has certainly been promulgated by plenty of people and it certainly has been backed up by analysts, but is it really that easy to make money on the App Store?

The economy of the App Store appears to be in flux. Independent developers are finding it more difficult to make enough money on the app store to sustain development, even with plenty of good press about the app. The race to the bottom for pricing apps is beginning to take its tole, forcing independent developers to adjust their monetization model.

Independent developer Marco Arment’s apps Instapaper and Overcast are fantastic examples of what pricing models used to work in the App Store and what the reality is today. When Arment first launched Instapaper on the App Store in 2008 he sold it for $9.99. On July 16th, 2014 Arment released Overcast, his third major iOS app. Overcast is available for free with a $5 in-app purchase to unlock features like Smart Speed and Voice Boost. Arment said the following about making Overcast free with IAP:

“I’m not that confident in the market for a paid-up-front app anymore, especially because I wanted to charge a good price for it. … If I launched today in the App Store I’m sure my day one sales at $5 would be decent, but, first of all, I know I got way more people [to try my app with] this model than I would have with [the paid up front] model. Second of all, I know over time that [the paid up front model] would be very hard to sustain because once the initial PR is over, and once all your friends and all your blog readers have bought it, and once everyone who’s going to write about it has written about it, then the sales of every app just tail off like crazy. They just drop. If you look at the graph it looks like a roller coaster. … If your app is paid up front that happens faster and it happens more severely.

“I’ve seen this happen. Instapaper was that model the entire time I owned it. It’s still that model today. I know that model very well. … I also know that in today’s App Store in a competitive category where I don’t even have the most features and people are very, very picky with what they want and what they don’t want, I knew that a $5 paid up front app was not a good long-term solution. … I saw with Instapaper there were so many people who I would come in contact with (in real life even, even family friends) … still using Instapaper Free, even two years after I discontinued it. There are so many people who … don’t pay for apps.”

Jared Sinclair, developer of apps like Riposte for App.net, Timezones, and Unread, faced these market pressures in particular with Unread. Unread was a well designed iOS RSS reader that launched at the sale price of $2.99 before being raised to $4.99. Sinclair worked tirelessly on the app: “I estimate that I worked sixty to eighty hours a week every week from July 2013 up until the launch of Unread for iPhone Version 1.0 in February 2014.” The app was covered by prominent Apple blogs and was even featured in the App Store. Despite the great coverage, hard work, and great app, Sinclair only made about $21,000 after taxes and expenses. Eventually Sinclair decided to sell Unread. His latest app, Time Zones, is free on the App Store with advertisements, though a $4.99 in-app purchase makes Time Zones ad-free.

John Gruber of Q Branch (and, of course, Daring Fireball and The Talk Show) recently opened up about why he and his colleagues raised the price for Vesper, the note taking app that I’m using to write these very paragraphs. Vesper launched in the summer of 2013 for $4.99, but had been on sale for $2.99 from the summer of 2014 until this winter. With the release of iPad support for Vesper Q Branch decided to raise the price to $9.99. John Gruber explained the pricing change, saying:

“Put another way, we’re going to charge something sane or die trying. We tried following the iOS App Store trend by pricing Vesper at just $2.99 for months. It didn’t work. Prices like that are not sane, and not sustainable, at least for well-crafted productivity apps. So Q Branch is drawing a line in the sand, and we hope other iOS developers will follow.”

These developers are attacking the same problem from different perspectives. Arment and Sinclair saw the trend in the App Store towards free with in-app purchase and adapted the pricing models for Overcast and Time Zones accordingly. Q Branch, on the other hand, is trying to reverse the trend. Both models are compelling, and more importantly, both models point to the realities we’ve seen on the Play Store for some time.

What Kinds of Apps Are Successful on Android?


While Android may not be known for being the platform that many developers work on first, it is a platform that has a vibrant development community with plenty of developers that are able to make a living from their Android apps. The key is finding the right app category and the right business model.

AgileBits is a great example of a developer that was primarily Apple focused, but recently brought 1Password to Android in full force. To be clear, AgileBits had an Android version of 1Password as far back as 2010, but the app only allowed users to read their usernames and passwords, not add any new credentials (or any of their other more advanced features). The app stayed in that condition for almost four years before being relaunched in the summer of 2014 with a complete redesign to better match Android’s aesthetic and add full functionality to the app.

“We wanted the app to be accessible to everyone,” says CEO Jeff Shiner. “We know many people have multiple devices on different platforms. We want them to be able to secure their passwords everywhere from an app that feels like 1Password, but that also feels native to the platforms they use, whether they be OS X, Windows, iOS, or Android.”

Part of making the app accessible to everyone meant AgileBits changing their monetization strategy. Starting with their Android release AgileBits made 1Password completely free to use with a one time $9.99 in-app purchase to unlock pro features (the iOS app soon followed suit with the same pricing strategy). Users are able to try the premium features in the app for 30 days before it reverts to read-only functionality.

The most famous example of a developer succeeding on Android is Shifty Jelly. Shifty Jelly, which is behind the popular podcast client Pocket Casts, hasn’t been successful on Android just recently either. Way back in December of 2011 Shifty Jelly’s Russell Ivanovic reported that the company was making the majority of their sales for Pocket Casts on Android. By 2013 Ivanovic reported that Pocket Casts had sold 5 copies on Android for every copy they sold on iOS.

What made Pocket Casts successful on Android where other apps have failed? I think the major reason is that Shifty Jelly made a killer podcast app on a platform that was in desperate need of a decent podcast app. Google provided Listen for a few years before discontinuing it in late 2012. Listen was never a good podcast app, but it was good enough to get the job done. Pocket Casts, on the other hand, was a great podcast app and has continued to iterate and improve to the point where I consider it to be the only podcast app to consider on Android.

The other reason I think Pocket Casts was successful is that it is sold for a fair price. Though that price has shifted over the years, it was high enough to support development and the expansion of Shifty Jelly’s team, but low enough that it seems reasonable to many. Pricing is always a tremendously difficult part in releasing and selling an app and Shifty Jelly did well in this regard.

Shifty Jelly shows that there is absolutely a market for paid apps on Android, but you have to make something that people want and sell it at a fair price. Determining those factors is incredibly difficult, but that’s been the reality on iOS and Android for years now. The days of selling software for $50 are gone. Freemium and cheap paid apps are here to stay as are the millions of users for each platform.

Does it really matter?


For smaller development teams the cost of supporting Android up front may be prohibitive, but there is simply no excuse for large companies like Facebook who have large development teams and effectively endless resources to bring their products to both platforms simultaneously. Companies like Shifty Jelly make it clear that success can be found on the Play Store just like it can be found on the App Store, but developers for both ecosystems need to be cautious with pricing in order to maintain enough income to continue development.

But what about for users? Does it really matter that Android users tend to get apps later than iOS users? This is a tough question to answer because it varies by experience and priorities. Having lived on iOS for the past four years I can say that I’ve enjoyed having access to pretty much every app I want, but I also can’t think of many apps that I can’t get on Android. I can, however, think of plenty of features and options that I can’t get on iOS.

While it’s not an intended compromise, I do think that is the compromise users have to consider. What’s more important to you: having the latest apps first or having the best features first? Most of Android’s best features eventually make it over to iOS and most of iOS’ best apps eventually make it over to Android too, so which do you want first?

Why is Android Still the Second Platform Developers Work On? is a post from: Droid Life



from Droid Life http://ift.tt/1BMwLa5

Microsoft Launches Office Suite of Apps to Google Play for All to Download

The Microsoft Office suite of apps, including Word, Excel, and PowerPoint are now out of Preview for Android smartphones, downloadable by all over on Google Play. Previews for each app were made available back in mid-May, but apparently testing went so well, public builds are now rolling out. 

According to the Office team’s blog post, during the preview period, the apps were tested on over 1,900 different Android phone models in 83 countries, with thousands of users providing feedback. Even a few of the user-requested features, such as easier syncing to Google Drive and Box, have been built-in to these builds today.

If you are looking for the tablet Office apps, you can find those here.

For all of your Microsoft Office needs, head on over to Google Play now.

Play Links: Office | Excel | PowerPoint

ViaOffice

Microsoft Launches Office Suite of Apps to Google Play for All to Download is a post from: Droid Life



from Droid Life http://ift.tt/1Nb8n2z

IFTTT Introduces the Android Battery Channel to Help You Conserve and Track Battery Life

If This Then That, better known as IFTTT, introduced a new Android Battery channel today to help all of us better manage battery life, trigger related actions when our phone is charging or not charging, and maybe even squeeze out a bit of extra juice when we are in the danger zone. The channel is live through the web, but does come in an update to the Android app as well. 

With the Android Battery channel, you can cook up recipes that do simple things like send you an email or SMS whenever your battery gets low. If that seems silly, think about something like having your phone automatically turn off WiFi or Bluetooth as your phone hits a certain percentage. Or maybe you just want your phone to send a notification to your Android Wear device as its battery dwindles. You could even go as far as to have the lights in your house blink when your battery has about had it.

Forget battery life for a second, though, and think about other triggers. Like, say you plug in your phone every night before you go to bed – you could have an IFTTT recipe that then turns the temperature down in your home the minute that happens. You could also have it turn the temperature back up when you unplug in the morning.

Outside of the Android Battery channel, the update brought with it Trello and Weebly channels, recommendations in your feed, and 2-factor authentication.

Play Link | IFTTT Battery Channel

IFTTT Introduces the Android Battery Channel to Help You Conserve and Track Battery Life is a post from: Droid Life



from Droid Life http://ift.tt/1CsTnY2

Qi Wireless Charging is About to Get a Whole Lot Faster

The Wireless Power Consortium (WPC) announced this morning that a new Qi wireless power standard specification “paves the way for fast charging of mobile phones.” In other words, wireless charging will soon have fast charging capabilities, similar to what is found in devices currently equipped with Qualcomm’s Quick Charge 2.0 technology. I’ll say that again – wireless charging is about to be fast, just like turbo or fast charging is. 

The new specification makes it possible for wireless chargers to deliver 15 watts of power to phones, which means decreased time required to charge. Those who currently own wireless chargers know that this is insanely good news, since current wireless chargers are far less than quick and not even in the conversation of fast. Any improvement is welcomed, but the WPC makes this new spec sound like it could be just as fast as wired fast charging, where a phone can reach 60% charge in as little as 30 minutes.

Oh, the news only gets better. According to the WPC, the new Qi specification will apparently be backward compatible with all existing Qi products. I would assume that they mean phones that are Qi-compatible. My guess is that you will still need to buy a new fast Qi charger to take advantage.

How exciting.


WPC Increases Power, Improves User Experience with New Qi Wireless Power Standard Specification

Latest Update Paves the Way for Fast Charging of Mobile Phones

PISCATAWAY, N.J., June 23, 2015 – The Wireless Power Consortium (WPC), the driving force and leader in the global adoption of wireless power technology, today announced that the latest version of the Qi specification now makes it possible to deliver 15 watts of power to mobile phones that support wireless fast charging. This Qi fast charging feature enhances the charging experience by decreasing the time required to wirelessly charge devices.

Several manufacturers already offer wired fast charging for their devices, providing as much as 60 percent charge in as little as 30 minutes. The latest Qi specification empowers them to extend this speed to wireless charging as well. Once again this is a first in wireless charging, creating more choice for consumers in the eco system of Qi-compatible products, an ecosystem that already offers the largest choice in wireless chargers, addressing the many different needs of consumers at home and on the move.

“With a deployed base of well over 50 million units, hundreds of registered products and users all around the world, we understand the importance of a specification that supports innovation,” said Menno Treffers, chairman of the WPC. “This release marks an important milestone for Qi, introducing the first higher power class and paving the way for our members to address more demanding applications with products that work seamlessly with the installed base of Qi-compatible products.”

In addition to the new Qi specification, the WPC also approved the test procedures and tools needed to verify that fast charging products are compliant with the new Qi specification, as well as being backward compatible with all existing Qi products.

The new specification is initially available only for members of the Wireless Power Consortium. It will be made available as a public document at a later date.

Cheers Jigga_Z!

Qi Wireless Charging is About to Get a Whole Lot Faster is a post from: Droid Life



from Droid Life http://ift.tt/1J5nauD

Related Articles

Related Posts Plugin for WordPress, Blogger...