x PhoneArena is hiring! Reviewer in the USA

24 hours with the Nexus 7: it's not all butter

24 hours with the Nexus 7: it's not all butter
Those of you that placed your pre-orders for a Nexus 7 in the Play Store may have been lucky enough to get your new Google tablet yesterday. To mark 24 hours with the new Nexus tablet, we wanted to talk about one of the more annoying issues that may not have been talked about yet, but is an issue that early adopters have to face every time a new Nexus device is released. 

The Nexus 7 hardware is solid - the device is a great size, it's fast, and really the only noticeable compromises are in the lack of a back-facing camera, and in the quality of the display. The camera may not be something you'll care about in daily use, but does cause issues as we'll get to, but the display is still good enough for most users. The Jelly Bean software is a great update that really does make Android feel better; it's smooth and responsive, and everything in the system seems to work just fine. The trouble isn't with the system, but with the app ecosystem. 

This isn't the same old rant that you've heard about the Android market being light on tablet-specific apps, because honestly, that's a load of bunk. Sure, there are some big name developers (Twitter) that haven't bothered to optimize their apps for tablets, but if you really care that much, there is almost always an alternative. And, the apps made by quality developers look great no matter what device you're using because Android uses responsive design principles which allow for incredible elasticity in apps. The issue we have is in the random apps that suddenly lose compatibility with new versions of Android or new devices. 

If you search for an app that is incompatible, it won't appear in the search results, which is a very good option. The trouble is that search also has an auto-complete function, which will send you directly to the app page for an app regardless of if it is compatible or not. If you search for Amazon in the Play Store from a Nexus 7, it won't show in the results, but as you're typing "Amazon", it will offer a direct link to the Amazon Mobile app page, which is troublesome since you can't install the app. 

Missing hardware

One of the things that Google did remove apps from search results and to reduce problems with compatibility was to have apps mark when they would need specific hardware features. So, if your app needs a camera, GPS, compass, etc. and the device doesn't have that feature, you won't be allowed to install the app, or even find it in the Play Store (unless you have a direct link to the app page). This is a good idea in most cases, because you don't want a camera app on a device with no camera, or an augmented reality app on a device with no GPS or compass. For example, it's perfectly reasonable that Instagram would be incompatible with the Nexus 7 at launch. The Nexus 7 is a device without a back-facing camera, so compatibility with an app centered on taking photos may be an issue. That's perfectly reasonable, and not something that we'd really get to annoyed about. 

However, when that same issue causes incompatibility with an app that isn't focused on taking pictures, just offers a peripheral feature that would need access to the camera, that's a bit more annoying. For example, if you own a Nexus 7, you may have noticed that the Amazon Mobile app is incompatible with the device. We can't say for sure that the incompatibility is caused solely by the lack of a camera, but Amazon Mobile (and the Amazon Price Checker app, which is also incompatible) uses the rear camera to scan barcodes or take pictures of items for comparison. It seems reasonable that this would be the problem with this app, because the Google Shopper app is also incompatible with the Nexus 7. Of course, the Price Checker and Shopper apps are centered around the camera functionality, so that we can understand, but Amazon Mobile is not. With Amazon Mobile, the camera functionality is non-essential, but the app still doesn't work. 

Developer responsibility

The biggest problem though is with the developers. There is no reason why Amazon should have made a back-facing camera a requirement for using Amazon Mobile. Other developers haven't made it a requirement when the functionality is non-essential. For example, the ING Direct app, which allows for depositing checks by taking a picture, or various instant messaging or social networking apps don't require a camera, even though there are camera options in the apps. And, it is all on the developer to make the choice. Facebook and Twitter allow you to take pictures and post them, but neither app requires a camera. Alternately, Hookt (a BBM clone) does seem to require a camera. 

Again, the camera may not be the only reason for incompatibility with the Nexus 7, but Amazon Mobile does work on tablets in general, so this is the only reasoning that makes sense. Another issue that is more prevalent than it should be is that the DPI requirements of an app can cause issues with compatibility, and this really does seem like a problem caused by lazy developers. As we mentioned earlier, Android uses responsive design, so no matter what the screen size or resolution (and therefore DPI), apps should work if developers have written them correctly. Case in point, Super KO Boxing 2, a Punch-Out! clone by Glu Mobile hasn't been updated since March of 2011, and that update was only to add Xperia Play optimizations. But, the game has run perfectly on both Ice Cream Sandwich and Jelly Bean, both of which came out after the game was last updated, and works perfectly on the Nexus 7. 

On the other side of things, NBA JAM by EA SPORTS was released in March 2012, but still needed an update just to work on a Galaxy Nexus running ICS, which had been on the market for about 5 months at that point; and, it now needs another update in order to run on a Nexus 7. We've reached out to EA SPORTS about the issue, but haven't gotten a response yet. 

The two faces of Nexus

All of these issues will slowly be weeded out as apps are updated, and Google has made sure that developers have access to the Jelly Bean SDK as soon as possible in order to get these issues fixed quickly. Unfortunately, this is a solution designed to work within the problem of slow updates rather than one that can help to push updates faster. The idea is that developers will get all of the bugs ironed out before Jelly Bean is pushed out to the majority of handsets, which could be a year from now for all we know. Given the way things work in the Android ecosystem, this makes sense, but it doesn't really work with the idea of Nexus devices. 

We've questioned before what Nexus really means these days. It used to be that Nexus was not just pure Google, but it was a developer reference device, and a device designed for early adopters. Early adopters know that there will be bugs and issues like the ones that we've described, so they can look past the small issues and have patience until they are sorted out. The trouble is that more and more Google is pushing the Nexus brand into the mainstream, to place it as a real choice for the average consumer. We saw this change with the Galaxy Nexus, and the $200 price point of the Nexus 7 is another indicator of this push. 

Unfortunately, average customers don't take well to small but consistent bugs and issues. The Nexus 7 is selling out, and it isn't just early adopters buying the tablet. So, when an average customer boots up their new tablet only to find that Amazon Mobile or NBA JAM is incompatible, they will no doubt be frustrated, especially since the Play Store doesn't give explanations as to why apps are incompatible. If the troubles persist, we wouldn't be surprised to see Google made incompatibility notices more verbose, because it really does seem as though Google needs to shame developers a bit more in order to get the Play Store in order. 

59 Comments
  • Options
    Close





posted on 18 Jul 2012, 20:08 23

1. Synack (Posts: 681; Member since: 05 Jul 2011)


Sooooo it's a new device are there are new device problems that will be solved with time...... welcome to technology PhoneArena.

posted on 18 Jul 2012, 21:36 8

13. gallitoking (Posts: 4721; Member since: 17 May 2011)


I agree specially with half baked devices... being rushed to the public...

posted on 18 Jul 2012, 23:33 4

18. Mxyzptlk (unregistered)


I miss the days of quality control department.

posted on 19 Jul 2012, 00:51 4

24. Sniggly (Posts: 7305; Member since: 05 Dec 2009)


I missed you. Hello sunshine.

posted on 19 Jul 2012, 08:34 4

31. MichaelHeller (Posts: 2707; Member since: 26 May 2011)


Well, we do have quality control here and galito just earned himself his 3rd warning with that comment

posted on 19 Jul 2012, 03:36 1

26. Henrik (Posts: 141; Member since: 18 Feb 2012)


The R&D (the project from start to finish) was 4 months on this device, Google even said so themselves. So, yeah, "rushed" is quite spot on :-)

posted on 19 Jul 2012, 08:59 1

36. remixfa (Posts: 14605; Member since: 19 Dec 2008)


how much R&D do you need with an established tablet maker using parts that are already available and an OS that was just finalized?

posted on 04 Aug 2012, 07:28

59. Henrik (Posts: 141; Member since: 18 Feb 2012)


You answered it perfectly all by yourself :-)

If you want to make a product that's unique and actually feels premium, you do as Microsoft and put some actual effort behind it. If you want to do some cheap ass me-too product, you do as Google and just screw already available hardware parts together and call it a day.

Thanks for helping me out! ;-)

posted on 19 Jul 2012, 18:03 1

52. sithman (banned) (Posts: 299; Member since: 21 Apr 2012)


U guys don't give iOS products that out. Just admit no products r perfect software, or hardware wise. Oh, and I'll give this comment the first thumbs down.

posted on 19 Jul 2012, 18:04

53. sithman (banned) (Posts: 299; Member since: 21 Apr 2012)


Damn I trid to thumbs down it for the androiders but it said I can't cuz its my comment. Go ahead droiders hook me up with the thumb downs

posted on 18 Jul 2012, 20:08 12

2. Sniggly (Posts: 7305; Member since: 05 Dec 2009)


I agree. Devs need to get their act together, and Google should work harder with them to do so. For instance, releasing the tools and code sooner before release and asking the Devs to get the updates out before the deadline. Maybe take away editor's choice status for the big names if they fail to do so.

posted on 18 Jul 2012, 20:11 14

3. nak1017 (Posts: 328; Member since: 08 Jan 2010)


Well, nothing that can't be fixed in a week or so... small price to pay for a top-notch $200 7" tablet

posted on 18 Jul 2012, 21:35 2

11. E.N. (Posts: 2610; Member since: 25 Jan 2009)


a week or so? I think you're being a tad too optimisitc

posted on 19 Jul 2012, 00:08 9

21. remixfa (Posts: 14605; Member since: 19 Dec 2008)


your confusing a branded tablet with the Nexus. When google has an update, it rolls out immediately on anything labeled "Nexus" that isnt tied to a carrier (cough cough VZW G-Nex)

posted on 19 Jul 2012, 08:33 1

30. MichaelHeller (Posts: 2707; Member since: 26 May 2011)


And I think you're confusing the issue. We're not talking about an issue with the tablet itself, but with various apps in the Play Store, so a week would be extremely optimistic for those devs to fix things

posted on 19 Jul 2012, 09:03

37. remixfa (Posts: 14605; Member since: 19 Dec 2008)


I'd expect the major devs like EA to fix NBA jam within a short time frame. The more minor devs might take longer, but for the most part they've been pretty quick to fix issues in the past. Its not like all games/apps need a fix. Like you said KO boxing hasnt been updated in a year and still works perfectly.

However, knowing EN's borderline troll posts, he was probably talking about "updates" in general for Android, aka system updates... which is what I was responding to.

posted on 19 Jul 2012, 09:57 2

41. MichaelHeller (Posts: 2707; Member since: 26 May 2011)


You actually have it backwards. Major devs tend to take longer to update because they have more projects taking up their time. It took EA over a month to update NBA JAM for ICS, but most of the smaller devs made any necessary fixes within a couple weeks.

posted on 19 Jul 2012, 09:11

40. nak1017 (Posts: 328; Member since: 08 Jan 2010)


I'm using Amazon's Mobile App right now and according to the article, it didn't work on the N7.
So no, it's not just optimism...

posted on 19 Jul 2012, 10:01

42. MichaelHeller (Posts: 2707; Member since: 26 May 2011)


Amazon Mobile is still listed in the Play Store as incompatible with the N7.

Did you sideload the app? It would certainly work sideloaded, but I'm just talking about getting it through the Play Store.

posted on 18 Jul 2012, 20:20 9

4. shelley.bevacqua (Posts: 80; Member since: 27 Aug 2011)


The author is right about novice tech buyers and their frustration with bugs in a product, function or application. I expect bugs, crashes, etc... I just love tech and innovation.
Still waiting for my Google Nexus 7 tab to arrive.

posted on 18 Jul 2012, 22:39 4

16. LionStone (Posts: 843; Member since: 10 Dec 2010)


Not any more frustration than any other piece of technology/electronics.

posted on 26 Jul 2012, 07:28

56. mcbeav (Posts: 3; Member since: 23 May 2011)


I disagree, for the average consumer, this will be an issue. The average consumer has a hard time understanding things like this. I know from working in the cell phone biz for a few years. For some people, you can explain it to them a million times, they just won't understand. For someone like yourself, or most people on here, your statement is true.

posted on 18 Jul 2012, 20:21 3

5. shelley.bevacqua (Posts: 80; Member since: 27 Aug 2011)


My fried got the Galaxy Nexus based on my recommendation. That was a mistake.
She has problems with her screen and AOL email account. Yes she has AOL.

posted on 18 Jul 2012, 20:25 4

6. Sniggly (Posts: 7305; Member since: 05 Dec 2009)


Have you tried another mail client like K9 with her? I heard that Aol doesn't play nice with the stock Android clients.

posted on 26 Jul 2012, 07:31

57. mcbeav (Posts: 3; Member since: 23 May 2011)


the phone is not for the average consumer, i used to work for one of the big 4, and we sold the galaxy nexus ( which limits it to one of 2 cell companies i worked for. ). This phone was returned 9 times out of 10. The biggest complaint was battery life. The average Joe just didn't seem to take to this phone. People really liked stock ICS, just not the phone itself

posted on 18 Jul 2012, 20:27 5

7. sudbury78 (Posts: 136; Member since: 12 Jul 2012)


Don't mess with an iPad. You can't win.

posted on 19 Jul 2012, 04:19 4

28. HTCFreak (Posts: 156; Member since: 17 Jul 2010)


If someone says: don't mess with the Nexus 7, he will get thumbed up.
If someone says: don't mess with the iPad, he will get thumbed down.
That's the way this weird world works now :(

posted on 19 Jul 2012, 08:36 2

32. MichaelHeller (Posts: 2707; Member since: 26 May 2011)


All depends on context. If this comment were on an article about the iPad, the thumbs would likely be reversed. Similarly, you can't expect to go into Yankee Stadium wearing a Red Sox jersey and not hear some boos.

posted on 19 Jul 2012, 13:19 2

46. manzl (Posts: 24; Member since: 04 Oct 2011)


u got that ryt.. but why r u talktive all of a asudden..

posted on 19 Jul 2012, 11:43 2

45. bayusuputra (Posts: 963; Member since: 12 Feb 2012)


but the thing is, N7 is not Google's answer to the iPad, it wasn't meant to be the competitor for iPad. It's another class on its own. Not even the same with that of Kindle Fire.

Obviously N7 can't win, right?

Want to comment? Please login or register.

Latest stories