8 ridiculous gigabytes

Software

App usage

It appears that Apple yesterday introduced a new iPhone 5c with 8GB of storage. CNN Money writes that “The 8 GB edition will only be available in the United Kingdom, France, Germany, Australia and China.” I won’t discuss this move from a strategical or financial standpoint — though I still think that at £429, versus the £469 for the 16GB version, it’s still too expensive a model. No, what I want to point out is that, today, offering a device like the iPhone with just 8GB of internal storage is simply ridiculous. It could work if the App Store didn’t exist, but let’s be frank here: 8GB are barely manageable once you put music on the device and start shooting photos and videos.

The picture above is the current Settings > General > Usage screen from my 16GB iPhone 4. Those are the apps that occupy the most space on the phone. Note that I still haven’t put back some of the music I removed before installing iOS 7.1 (before I had 1.5GB worth of music). If my 16GB iPhone 4 has an actual 13.5GB available out of the box, we can assume that a 8GB iPhone will have roughly 6GB of actual storage available to the user. Look at the picture above once again. If you calculate how much space those apps take up combined, you’ll have a total of almost 4.4GB. The same situation on a 8GB iPhone would be even less manageable.

A lot of iOS apps are quite lightweight on average, but have a tendency to grow in size when you use them regularly. That’s because they start accumulating data, documents, caches, etc. Hipstamatic, taken alone, weighs less than 40MB, but when you start buying and downloading new packs of lenses/filters, the app takes up more and more space. Hipstamatic also stores the photos you take in its own camera roll. You can keep its size under control by periodically deleting the photos from its camera roll (if you auto-save them to the iPhone’s Camera Roll). Same goes for apps like VSCOcam, KitCam and Camera+. I do that every now and then, and I have a 16GB iPhone. On an 8GB iPhone, if you like to take photos and use different third-party photo apps, you’d have to perform this kind of maintenance constantly, and it’s not fun. Also, the 8‑megapixel iPhone 5c camera shoots photos & videos with better resolution than the 5‑megapixel camera of my iPhone 4, thus taking up more space. 

Other apps are a bit more difficult to manage. As far as I know, there’s no direct way to prevent Spotify from bloating. I guess those 365MB (almost 900MB on my iPad 3) are cached data for the most part, and so far the only way I’ve found to eliminate such cache has been to manually delete and reinstall the app. 

And even if you don’t shoot a lot of photos and videos (come on, now, you buy an iPhone 5c and you don’t take photos?), even if you keep your music library to a minimum, what about other things like podcasts, books, dictionaries, drawing apps? What about games? Some of the best games for iOS take up a lot of space. I had to eventually get rid of a couple of games because together they took up more than 2 gigabytes.

An 8GB iPhone 5c with roughly 6GB of actual available space is simply a crippled device if you ask me. And with those prices, it’s just too expensive to make sense. It’s time to make 32GB the default option, and go up to 64 and 128GB, and keep the 16GB as the ’emerging markets’ version. And to increase the 5GB offered with iCloud free accounts, but that’s another story.

Geek. Not chic.

Tech Life

Craig Hockenberry has written a truly insightful article, Wearing Apple, analysing how Apple could approach the category of wearable devices. The steps in Hockenberry’s reasoning leading to his conclusion that Apple may introduce a ‘ring’ rather than a ‘watch’ (in quotes because those would be more than just a ring or just a watch) are sound and logical. What Hockenberry writes in The Product section of his piece makes a lot of sense. 

Still, I think that a ring would be even more difficult to market, no matter how smart or ‘Apple-designed’ it can be. 

Importance and meaning

A ring is a traditionally symbolic object to wear. I’m aware of the dangers of anecdotal evidence, but most people I know don’t wear rings lightly. Whatever the amount of rings they wear, each one is there for a reason, each one is there because it means something. What you wear on your finger is typically more important than what you wear on your wrist or neck. It feels more intimate. Entering this space with a technological device is not impossible, but I have the feeling it’s a minefield. I also have the feeling it would appeal to a rather limited demographic/target — the intersection of young and geeky people. What about other people outside of this demographic? And whatever this Apple smart-ring can offer, it doesn’t sound strong enough to make (these) people wear such a device. It could actually prove easier and more practical to make them wear something on their wrists.

Permanence

Together with intimacy, a ring is usually associated with permanence. A lot of people don’t wear watches all day, and most people don’t wear watches 24/7. I’ve never worn rings, and when I got married I remember struggling with having to wear my wedding ring, I really had to get physically accustomed with its presence, knowing full well how meaningful it was and what represents. After a few months, my wedding ring became part of me, and today I don’t even notice its presence. I bet a lot of tech companies would love people to wear smart wearables permanently, devices that just ‘disappear’ after a while. But I’m not that sure regular people want this. I think they would prefer something they feel they can remove anytime they want. I think that for them to accept a piece of technology in such an intimate, meaningful place, it has to be a really, really compelling device. I’ll use the same Tim Cook quote cited by Hockenberry:

To convince people they have to wear something, it has to be incredible. If we asked a room of 20-year olds to stand up if they’re wearing a watch, I don’t think anyone would stand up.

And yes, maybe if we asked a room of 20-year olds to stand up if they’re wearing a ring, more people would stand up, but that doesn’t necessarily mean they would be glad to have a smart-ring on their fingers. And if they were, it would be interesting to try the same experiment with a room of 30-year olds and 40-year olds. True, nobody’s saying that a smart-ring has to be worn permanently — you could wear it just when you need it and take it off when you don’t. But again, that’s not how people typically view rings. They see a ring and think ‘permanence,’ ‘intimacy,’ ‘on my finger,’ and do they want that thing that vibrates, tracks, communicates its presence (and your presence) there on their finger? Hmmm. I don’t know.

Geek. Not chic.

Do you remember that famous 1998 advertisement for the first iMac model? Its tag line was Chic. Not geek., indicating how that new Mac wasn’t simply technologically advanced, but also something stylish to look at and to have. In judging wearable ideas, solutions, mockups, actual products, I mentally reverse that tag line and it works every time. The Pebble, the Samsung Gear, you name it. Imagine an ad that says ‘Geek. Not chic.’ for these devices — it works. Hockenberry’s idea of an Apple smart-ring is great and well thought-out, but it still retains a geeky essence:

[This wearable device could support iBeacon.] Let this sink in for a second: your wearable device is transmitting a signal with a unique identifier that can be picked up by an iOS 7 device. And the proximity detection is sensitive within a few inches. Presumably, this signal could be also be detected on your Mac as well, since they have supported Bluetooth 4.0 since mid-2011.

By wearing this ring on your finger, your devices can know how close you are to them.

This opens up a world of possibilities: imagine the joy we’d all feel when a notification only popped up on the device we’re closest to. Right now my ring finger is hovering over my MacBook Air’s keyboard by 2–3 inches, while the phone in my pocket is over a foot away. Notification Center needs this information.

I read this and ask myself — and ask you: Look around you as you walk down the street. How many people would be so thrilled, so excited by this, as to want to wear a tech ring on their finger? How many people share the problems that this smart-ring solves for Hockenberry and other Apple geeks?

The power of attraction

As I’ve recently emphasised, Marco Arment nails it when he comments:

Apple’s previous blockbusters — Mac, iPod, iPhone, iPad — were all in categories that people really wanted, and there was hope of something good existing within what was technically possible. There were halfway decent portable music players before the iPod, and people really wanted portable music players. Same for smartphones and tablets. 

A smart-ring (or smart-watch or smart-wearable) designed to be a companion device of another device in this Digital Hub 2.0 is going to work best (or even only) inside an ecosystem, and I see Hockenberry’s ring working really well if the user already owns a Mac and an iOS device. Every device produced by Apple since Jobs returned in 1997–98 has had a strong power of attraction over people. I’ve seen a lot of people switching to Apple via the iPod, and a fair share of people switching to Apple thanks to the iPhone and the iPad. I don’t see an equally great power of attraction in a ring as Hockenberry describes it — or in any hypothetical Apple smartwatch for that matter. Unless, of course, such device can offer innovative and independent uses. In other words, unless it’s a cool device that 1) has enough standalone functionalities that people may want to purchase it, and 2) teases users by making them realise how so much better it would work if it were used in combination with other Apple devices. 

Too many variables

Throwing out products and see what sticks is not part of Apple’s culture. Apple doesn’t introduce a device lightly and I can only begin to imagine all the challenges they’re facing with the wearables category. Where to wear such a device? What features should it offer? What could make it compelling to the widest possible audience? Can it be used on its own, or is it going to work only in conjunction with another Apple device? Which problems does it solve? Which things can it do better than existing solutions? In what ways could improve people’s lives? (This, I believe, is the question that best captures Apple’s approach to designing new products.) Should it be just an expansion of Apple’s product offerings or should it also entice users of other platforms into switching to Apple’s ecosystem? And how? And so on and so forth.

Getting this product right is extremely difficult and the timing is also crucial, because now more than ever Apple needs to get it right. The anticipation and pressure from the media is reaching a point that a product fiasco at this juncture could have a dramatic impact on Apple. And there are so many variables to consider, which is what makes the wearables category such a risky operation. My guess is as good as yours, but I believe that whatever device Apple introduces, it’s going to be something unassuming at first, something that will make pundits think that Apple’s playing safe. Something that will not feel exactly like a tremendous breakthrough. But that will gather strength, features and scope by iterative refinements. And, of course, that won’t appeal only to geeks.

The difference between a pocket watch and a smartphone

Briefly

In his commentary on Craig Hockenberry’s article Wearing Apple[1], Marco Arment sums up exactly what I think about smartwatches, with clear brevity. He concludes:

[Smartwatches]: it’s a category that pundits and the tech media are telling us we want, but I’m not sure enough people really do.

And of course this morning, while flipping through articles on Flipboard, I happen to see this one: Apple understands the difference between a pocket watch and a wrist watch, where the author, after recalling how the wristwatch came in use at the end of the XIX Century “when men in the military started strapping their pocket watches to leather straps around their arms,” writes:

Now fast forward to the iWatch. It isn’t here yet, and we are already reviewing, criticizing, and rejecting it before we have even seen it. Some people say, “I don’t need it. Why would I want an iPhone on my arm?”

I think you will want an iPhone on your arm, and in the beginning it will feel just as awkward as those soldiers must have felt when they first strapped their pocket watches to their wrists. To them, it felt unnecessary and maybe even made them feel a bit self-conscious. But after discovering how much easier it is work time into everything they do, the wrist watch became more than a convenience. It changed the outcome of wars.

And I thought about Marco’s words, quoted above.

The parallelism ‘from pocket watch to wristwatch’ = ‘from smartphone to smartwatch’ doesn’t really work as seamlessly as the author suggests. On the one hand, you have the same object, a watch, that’s made practical by strapping it to your wrist instead of being in your pocket and attached to your trousers or waistcoat. It changes location, but not its inherent functionality.

On the other hand, moving a smartphone from the pocket to the wrist poses multiple design challenges, but in a nutshell you simply can’t have on your wrist the same object you now carry in your pocket, because a smartphone does a thousand things more than a watch. It’s not that simple. Not even for Apple.

And I still think it’s not that essential, either. Why should I want to purchase a necessarily crippled device to wear on my wrist when I can have a full-featured, fully functional one in my pocket? 

(More thoughts about wearables and smartwatches in my article Wearables: thinking aloud.)

 


 

  • 1. Hockenberry’s article is really interesting and insightful, and I’m still mulling over it. I’ll probably write a few observations in the following days.

 

My trick to deal with the redesigned Shift key in iOS 7.1

Briefly

One of the most baffling changes in iOS 7.1, you will agree, is the redesigned Shift key in the virtual keyboard. There was nothing wrong with the way it was implemented under iOS 6 and iOS 7.0.x and I honestly can’t think of a reason to justify this change — it just seems so arbitrary. If you want to take a look at a comparison of the changes in the Shift key behaviour under iOS 6, iOS 7.0 and iOS 7.1, read Nick Heer’s impressions in his article Dot One.

Simply put, the new Shift key design is confusing. So I came up with a little trick to instantly tell whether the Shift key is engaged or not. The Caps Lock state remains recognisable in my opinion (the arrow symbol gets ‘underlined’, resembling the Caps Lock key on Apple’s keyboards), so I won’t mention it here.

The trick for me is to look at the Delete key. If Shift and Delete look similar (i.e. they have the same colour scheme), then the Shift key is not engaged. If the Shift key has an inverse colour scheme, then it is engaged.

Light Shift off

Fig. 1 — Keyboard with light theme. Observe the Shift and Delete keys: both have white pictograms on a grey background. This means that the Shift key is OFF.

 

Light Shift on

Fig. 2 — Keyboard with light theme. Here, the Shift key looks inverted if compared with the Delete key. This means that the Shift key is ON.

 

Dark Shift off

Fig. 3 — Keyboard with dark theme. Observe the Shift and Delete keys: both have white pictograms on a dark grey background. This means that the Shift key is OFF.

 

Dark Shift on

Fig. 4 — Keyboard with dark theme. Again, the Shift key looks inverted if compared with the Delete key. This means that the Shift key is ON.

 

I’ve found that since learning to look at the Shift key in connection with the Delete key, I can readily tell in which state the Shift key is at any moment. (I only need a moment to adjust when I use an app that still employs the old iOS 6 keyboard style.) If this doesn’t work for you, iMore offers another suggestion.

iOS 7.1 and the iPhone 4 performance

Software

Improved performance

This is what appears at the bottom of Apple’s iOS 7.1 page. I would have updated my iPhone 4 to iOS 7.1 anyway, but I was pleased to see such incentive nonetheless. I know a few iPhone 4 users who are still on iOS 6.1.x., and to those who refrained from updating to iOS 7 only because of performance concerns, I can safely say they can do so now. 

Come on, it wasn’t “unusable” before

But there’s something I just need to get out of my system first. I strongly disagree with those saying and writing that the iPhone 4 was “unusable” before, meaning on iOS 7.0 to 7.0.6. It was not. Of course, the iPhone 4’s hardware is old by today’s smartphone standards, and has its limits. And I admittedly didn’t rush to update it from iOS 6 when iOS 7 came out. But I’m glad I did, in the end. At the time, one of the articles that contributed to my wariness was this one by Ars Technica: New Lease on Life or Death Sentence? iOS 7 on the iPhone 4. It is a well written, informative article, but at the time it also led me to believe that iPhone 4 performance under iOS 7 was worse than it actually turned out to be.

Ars Technica has published another article about the iPhone 4 and how it performs under iOS 7.1, iOS 7.1 on the iPhone 4: As good as it’s going to get, which again I suggest reading because it contains useful information and even stopwatch-measured app launches comparing responsiveness under iOS 6.1.3, iOS 7.0 and iOS 7.1. But I don’t fully agree with the author when he refers to the iPhone 4 performance under iOS 7 as being ‘jerky’ and I think this sentence in the last paragraph is a bit exaggerated: If you’re sticking with the iPhone 4 for another year, iOS 7.1 makes performance tolerable enough that using the phone isn’t unbearable.

I’ve previously talked about my impressions on iOS 7 and how it performs on my iPhone 4. Read iOS 7 on the iPhone 4 and iOS 7, battery life, and the iPhone 4 for more details. In short, the only issues I noticed when updating to iOS 7 were occasional lags in UI animations and transitions, and occasional lags when using the virtual keyboard. Occasional being the key word. I concluded my article by saying:

The general performance is surprisingly good considering the aging hardware, and not disappointing compared to the situation under iOS 6. At least for how I use my phone. If you fiddle constantly with your iPhone, you may find certain transitions (lock screen to home screen, going in and out of apps, etc.) to be slower than before. I find them more pleasing and less ‘harsh’, but that’s me. 

And I absolutely stand by these words. 

I have the feeling that some who talk about the iPhone 4 being “unusable” under iOS 7 are people who are now accustomed to the performance of the iPhone 5, 5c and 5s, and having to go back to an iPhone 4 to review iOS 7/7.1 they find a noticeably worse user experience. That’s understandable. I don’t have faster smartphones than my iPhone 4 at the moment, and again I’m telling you that I’ve never found its performance under iOS 7 to be intolerable or the phone unusable. I never really felt it slower than under iOS 6, simply different. And the occasional lag or stutter was no big deal, really. Oh, and another detail that I rarely saw mentioned: I experienced just one random Springboard crash under iOS 7 on my iPhone 4 (a couple more on my iPad 3), so I can say that iOS 7 on my iPhone 4 has always been rather stable. Therefore I really can’t agree with Federico Viticci when he writes:

Indeed, iOS 7 on the iPhone 4 (and to an extent, the iPad 3) was, in my experience, insufferable: animations were slow, scrolling would often drop frames and stutter, and everything felt generally sluggish.

He’s not alone (just skim through the comments on both the Ars Technica articles I mentioned), but really, as an owner of an iPhone 4 and an iPad 3, sometimes I think I have some special versions of these devices, since my experience has been noticeably different. Again, please note that I’m not saying that the iPhone 4 is particularly fast under iOS 7. If you’re one of those teenagers I frequently see out and about furiously tapping text and chat messages with two thumbs, then your idea of speed, performance and responsiveness is going to be different than mine. What I’m denying, however, is that the iPhone 4 has been unusable or insufferably slow and sluggish under iOS 7. 

iOS 7.1 and the iPhone 4 performance: is it really better?

I haven’t been measuring response times with a stopwatch. What matters to me is the general feel, not the millisecond. But since updating to iOS 7.1 I’ve noticed better responsiveness overall. The interface feels snappier. Animations, transitions are faster. The iPhone 4 seems to be faster at waking up and unlocking the screen. Apps’ launch times are shorter, as are the ‘zoom in’ and ‘zoom out’ transitions when you launch an app and you quit it. Navigating screens and swiping throughout the interface feels faster. The multitasking interface is more responsive and I’ve noticed no visible lagging or stuttering when swiping to navigate the carousel of open apps. Notification Centre and Control Centre’s interfaces are faster to display and slide away, especially Control Centre, which seems to have a slightly bouncier animation than before and feels more responsive when invoked. 

Another improvement is in the virtual keyboard’s responsiveness. I didn’t have particular issues with the keyboard before, but admittedly sometimes it lagged, felt stuck, only to regurgitate everything you’ve typed when it looked as if it weren’t registering your key strokes (a phenomenon I like to call ‘cluster typing’). Under iOS 7.1 I have noticed no such lagging and the keyboard seems to be keeping up with my typing quite well. 

As regards to the built-in apps, so far I’ve noticed better responsiveness in Safari, Mail and Camera. The Camera app feels a tiny bit faster at launching, both when you tap its icon, and when you access it directly from the lock screen. Changing modes (Video, Photo, Square) feels slightly faster as well. Same for navigating photos in the Camera Roll. Battery life appears to be the same as before, which is nice.

All these improvements are noticeable, and I highly recommend updating to iOS 7.1 to all iPhone 4 users. If you’re still on iOS 6 simply for performance-related reasons, then updating to iOS 7.1 will give you a comparable experience. If you’re still on iOS 6 for mere æsthetic reasons, then I can’t argue with this type of personal preferences, but I’ll remind you that there hasn’t been a 6.1.6 patch for the iPhone 4 to fix the SSL/TLS security flaw (iOS 6.1.6 is available for the iPhone 3GS and the 4th-gen iPod touch only), so you’re using a device that is currently not secure.

(I may update this article in the following days if I notice other specific improvements worth mentioning.)