Archive for category Technology Trends & Looming Opportunities

The iPhone HD and iPad means Apple Hates Apps – That’s a Good Thing

According to Gizmodo, this is Apple’s next iPhone, importantly, to me, with a screen of 640×960. There has been a lot of kvetching around the Internet about the iPhone’s new case, it’s front facing camera, etc. but I think that people are missing the cooler picture here. Since the iPad’s resolution is 768×1024, and that the original iPhone’s screen is at 320×480, then we can only draw one logical conclusion: Apple hates apps.

Yup – I said it. There is no taking it back. I dare you to disagree. Well, at least some apps. The bad apps. The unloved apps.

hero-shop-pixi.png
pre-family-verizon-device.gifOne of the iPhone’s, and iPod touch’s early competitive advantages against the Android, Palm, Nokia, and Blackberry was it’s consistent development target. As a developer, a typical app that I built for the iPod touch would work just fine for the all of the iPhone platforms because they had the same input, same screen resolution, etc. If it worked on an iPod touch, then I really didn’t need to test it on, say, an iPhone 3G. Unlike, say, the Blackberry line, with several different resolutions, orientations, and input methodologies, developing for one model meant very little chance of it working on the other models. My early Blackberry development was a bit of nightmare. I screamed at Palm when, after making a game for them targeted at 320×480 on the Palm Pre, when they started shipping the Palm Pixi with resolution of 320×400. What kind of sadist company would do that to their developers? Don’t get my started on what it is like to test for a Nokia app. That fragmentation made it quite difficult to develop for them. The recent spat of resolution changes for the iPhone line, though, changes that Apple advantage (but don’t worry about Apple just yet).

pic1.jpgbb_phone_storm29550.jpgbb_phone_bold9700.jpg

Why would Apple do this? Well, partly, of course, is that they sorted of needed to get higher resolution screens for the iPad. But for the iPhones, those little screens are good enough, and Apple has never been known for introducing technology with out a corresponding and compelling uptick for the user’s experience. I think this is part of their strategy for culling their massive app catalog of the crappy apps. I don’t think you can underestimate how many of the apps in the app store basically don’t make any money. Stories abound about the app producer that spent $30,000 in development but only harvested $1,000 from the app store. There are countless more, and I know from first and second hand experience, of apps that, although costing less to develop, are only earning $100 in revenue over the life of the app. So, arguably, most, but not all, of the apps, just suck. Those developers will simply not re-invest the time and money to port them to the iPad or the higher-resolution iPhones.

This is win-win for Apple and the consumers. Apple still gets to rightly claim an un-godly number of apps in their catalog, but as the newer devices come online, those consumers will only normally see the apps designed for their device. As a new iPad owner, I really felt compelled to remove every iPhone app, except for the one or two that didn’t have an iPad equivalent and were actually important to my daily workflow.

My recent apps that I upgraded for to the iPad, Nightlight and Powernap: Forty winks anywhere meant some significant re-thinking of the app. I couldn’t just rely upon iPhone emulation mode – things didn’t look good without re-designing. Redesigning for a different screen is a big deal. The investment is significant. The looming changes in screen resolutions out of Apple is also having me revamp my whole programming workflow – something difficult for less sophisticate programmers and developers shops to pull off. Developing for the iPhone OS line just became a lot tougher.

What Apple could have done to make me think different? While in emulation mode, when zoomed in at 2x, I would have expected to see the fonts, for example, re-scaled. Imagine when you zoom-in in Safari, the text still looks awesome. Not the case for iPhone apps on the iPad. Graphic images also could also have been resampled/interpolated, like when you plop a DVD into a player attached to your fancy HD TV. Those DVDs, without extra processing, look pretty crummy. That crummy image was, originally, a big marketing angle for Blue-Ray purchases. But with good processing, a DVD actually looks pretty decent on an HD TV. Apple is a smart company – they could have done that, too, if they thought it important enough – they just didn’t.

This is all pretty good stuff. Apple wins. Consumers win. And, I think, independent developers will win because of fewer get-rich-quick developers out there trying to win the app lottery, undermining the economics. I, for one, welcome our new varying resolution Apple overlords.

  • Share/Bookmark

View Comments

My Talk from Blackberry Developer’s Conference: Cross Platform Strategies + PhoneGap

I recently returned from the excellent BlackBerry Developers Conference where I gave a talk on cross-platform development strategies.

  • Share/Bookmark

, , , , ,

View Comments

Grope Control, Better than Voice Control when Walking

So, I’ve been designing an app that is basically meant to be used by car drivers.  It’s tentative going to have full Voice Control for enhanced usability and safety.  It’s going to be a great app. I think.

Although I can totally identify with my lead user, a salesman type of guy that drives all over town, the app wasn’t really resonating with me now that I work out of my home office and spend most of my ‘commute’ either walking, biking, or on mass transit.  My automobile time is often with wife and family, so Voice Control would be terrible in-effective over the dins of a car full of talkers.  So what about me?

I’m a big fan of Apple’s new Voice Control, but although society apparently now accepts hearing one side of a phone conversation from people walking down the street, are they ready to accept that somebody saying, to no one in particular, ‘Next Item’, ‘Back’, ‘Postpone’, ‘Play songs by the Shin Shins’, isn’t a little crazy, or at least a little socially inept?  I’m not ready to be that bold trend setter.

Some grope motions we can recognize

Some grope motions we can recognize

So, how can we interact with our mobile devices while walking down the street?  If I presume that I’m wearing headphone, then I can image holding my phone in my pocket and using my phone for input if my app is giving me adequate audio feedback.  The phone could say into your ear “Your next appoint with Mr. Smith is in 15 minutes.  Tap once to acknowledge or tap twice to remind you again in 10 minutes.”  I’m excited about this and can image a whole set of utilities and games that I can use while moving around the city.  I’m calling this method of input “Grope Control,” though I’m hoping to get suggestions for a more politically correct name.

For the sake of completeness, I’ve started to enumerate some common input and output methods and came up with some names for some of the combinations, namely Classic Control, Voice Control, Grope Control, and Spy Control.  I like to name things.  I think the introduction from The Non-Designer’s Design Book put it well when it’s introduction concluded that “Once you can name something, you’re conscious of it. You have power over it. You own it. You’re in control.”

Output Options

Eyes Ears Touch Comments
X X X Great when the device has the users undivided attention and the user is holding the device.
X X   Good when the user is not holding the device, say, its sitting on a desk or is mounted to a wall or dashboard, but the user can still focus on the device.
  X   Great when your hands and eyes are occupied, like when you are one the move, either driving or walking.
    X Would be great for silent two-way communication, but the mainstream technology is currently limited to vibration on most devices and little 'clicks' on some devices like the Blackberry Storm.

We’ll ignore mouth and nose as useful output options, though its fun to think about.  Hmm, my phone smells musky, and tastes bitter, it must be time for my 3:30 appointment.

Input Options

Gesture Tap, Pinch, Zoom, Twist - requires two hands or a mounted device. One to hold the device and one to make the gesture.
Gesticulate Waving the device around, like shaking the device to 'undo' for the iPhone, or bowling for the Nintendo Wii. Requires arm movement.
Thumb One handed thumb control, where you hold the device in, say, your right hand, and then use your thumb for input.
Voice Say a command. Good in quiet places like car or living room. Not good for a bus or subway because its too loud and people would think you are crazy.
Buttons Some Apple headphones let you single click the button on the microphone to stop the song, double click to advance to next song, and press & hold.

Named I/O Combinations:

Name Outputs Inputs
Classic Control Eyes, Ears, Touch Gesture
Wild Classic Control Eyes, Ears, Touch Gesture, Gesticulate
Wild Muted Classic Control Eyes, Touch Gesture, Gesticulate (Wild Classic with the Mute on)
Voice Control Ears Voice
Grope Control Ears, Touch Thumb
Wild Grope Control Ears, Touch Thumb, Gesticulate
Spy Control Touch Thumb
Specialized Control TBD Buttons or specialized hardware

Scenarios

Scenarion Attributes Solutions
Driving Limited Eyes. Good audio. Not holding the device, so no haptic (touch) feedback. Voice Control
Walking down the street with headphones Maybe loud. Don't want to make a scene of yourself. Hands want to be in your pocket during winter weather. Grope Control
Walking down the street w/o headphone. Maybe loud and you don't want load noises coming from your pocket where you are holding your phone. Spy Control
Business Meeting Don't want others to hear or see your inputs. Spy Control
Movie Theater The phone is in your pocket, you can't see the screen and you can't hear the commands Spy Control
Standing in line at the airport Your hands are free, you aren't doing anything useful, but you don't want to draw attention to yourself. Muted Classic Control
Being old Many older people are moving away from computers, let alone iphone, because poor eyesight are decreasing finger control makes mouse usage difficult. Voice Control, (Wild) Grope Control.

Implications for the app producer

  • Know your user personas.  How and where will they be using your app? Ask yourself whether you want to limit your app to a single I/O combination, or do you want to allow, and budget for, multiple IO combinations?
  • You might also plan on spending some extra marketing effort in explaining and showing the benefits of your non-classic I/O options.  Can you imagine the virus buzz you’ll get as the first Spy Control app published.  Can you make a killer YouTube video to go along with it?

Implications for the app programmer

  • You’ll simply need a solid gesture library.  Apple is clearly working in this direction and now has a built-in and refined “Shake” detector.
  • Have a standard voice control browser for your platform would be useful.  You can test your voicexml stuff at voxeo.com’s site before putting into your app.
  • What would the voicexml equivalent for SpyControl be?

Implications for the DoD

  • Patent 6899539 addresses putting a trackball onto a weapon to provide (http://bit.ly/Patent899539) some mechanism to get feedback into a computer w/o taking your hands off of a weapon, say, your rifle.  The trackball approach presumes that your see a screen, which means you are not focused on your target.  Fundamentally the soldier needs more combat appropriate input methods.

    Image from patent with rifle and trackball

    Image from patent with rifle and trackball

  • Software robustness: If, say, a screen is damaged or, untrusted, should there be another input method available to the operator?
  • Share/Bookmark

View Comments

Voice Control is the new Touch, almost.

I’ve been playing around with my new 3GS for a few days now.  As you might know, it has some built-in automatic speech recognition (ASR) capability that Apple brands as Voice Control, good for making calls and operating the iPod.  There is now, however, no programmer interface to allow its system to control 3rd party apps – bummer.  I’d bet, however, that we’ll soon see Voice Control as a core iPhone capability for all apps – perhaps next year.  When will it come to the PC?  The future is murky. Importantly, though, the basic iPhone technology works pretty well.  Better than anything else I’ve used.  A thousand times better than the built-in bluetooth voice dialer my last car had.

For the first time in years, I found myself exploring my music collection.  “Play songs by Johnny Cash” begets “Playing songs by Johnny Cash,”  and then the classic crooner laments about love gone bad in Memphis.  This is even safer than using the in-car stereo because I kept my eyes on the road the whole time.  I found myself calling people.  Of course, driving while distracted is bad, but it was actually practical to call the house and tell the kids that I was on my way home without having to take my eyes off the road.  When ASR works well enough, you’ll want to use it. And use it in circumstances that were previously off-limits or much more dangerous.

There is a related technology in the iPhone called VoiceOver.  Designed for people with vision impairments, this uses a text to speech (TTS) voice synthesizer and basically verbalizes what the person’s finger is touching.  When you swipe between app screens, you’ll hear “Screen 3 of 11″ followed by a listing of every app on that screen.  Touching an app like PowerNap, prompts “Power Nap, double tap to launch.”  A double tap, anywhere on the screen, then launches the app.  This system works too, but not well enough. Among its various drawbacks, it still requires a lot of tapping.  So, although you don’t need to use your eyes, you still need to use your hands.

ImgDeviceVoiceControl1

Key Technologies

  • Automatic Speech Recognition (ASR)
  • Text To Speech (TTS)
  • Automatic or Semi-Automatic Voice Transcribing – for recording voice memos, and converting them into text.

Implications

… for the application producer

  • If your app would likely be used by somebody walking around, then start thinking about Voice Control now, while still in your design phase.
  • Improved voice control, with high quality voices and better recognition, may be worth an in-app purchase/upgrade.
  • With the Silver Market (retiring baby boomers) increasing, their eyes getting worse, their fingers hurting more, then maybe Voice Control is the way to  bring/extend apps to that huge market.

… for the developers

  • Think about Voice Control early in the design phase.  Don’t count on being able to elegantly retrofit your eye & finger focused app into both eye & finger and ear & voice.  Don’t believe me?  Then ask yourself how many of the mouse & click focused apps were easily ported to the iPhone’s finger-based system?
  • Jump-start your mind by testing out some existing apps with Accessibility turned on.  It was an enlightening experience for me.
  • Open-source SDKs here are seriously lagging behind the commercial implementations, but they might be good enough to act as a preview or teaser, and allowing  only serious users to purchase the upgrade.
  • The commercial implementations are just now starting to think about licensing their SDKs.

… for R&D and DoD

  • Imagine mobile applications that are useful w/o hands or screens. We’re used to thinking about the field utility of such systems, but what about the non-combatant, or at least those not all the way on the front line.
  • To following this line of thought, haptic feedback is just coming to the consumer space – so if you can’t imagine soldiers chatting away all day to their PDAs, can you imagine them gesturing to one, without ever seeing the screen.
    •  

      hand signals

      Not sure these are quite the right commands

  • For application survivability, if the screen is damaged, say, by a bullet, shouldn’t the software still be able to function via alternative input methods, like voice?  It might not be as efficient in some cases, but perhaps it would be better than nothing.
  • Low power consumption: software capable of voice control wouldn’t need a screen.
  • Weight: No screen equals lower weight.
  • Share/Bookmark

, ,

View Comments

Digesting last night’s HBS lec…

Digesting last night’s HBS lecture “Global Megatrends: Next Billion $ Opportunities”
Summary: Urbanization, Old People
http://bit.ly/75HTh

  • Share/Bookmark

View Comments

Future of Newspapers and Journalism?

So, talking about the future of the newspaper industry is what all of the cool kids are doing.  Some have said the that the better question is not whether the newspaper industry can be saved, but whether journalism can be saved.  Ok, but let us talk about the newspaper industry.   Can the New Yorks Times, Boston Globe, and LA Times be saved?  It’s like asking whether Kodak, Poloroid, and Fuji Film can be saved.  Or Xerox.   The answer is that yes, they can be saved, but they look very, very different than they appear today, and even then, only if they are willing to go through the transformation.

As an experiment, I’ve started a discussion regarding what a mobile version of Boston.com should have here.

By the way, Apparently Arriana Huffington (sp?) has started a foundation to sponsor lone journalists – which is cool, and a start.

  • Share/Bookmark

View Comments

Brushing up on my Guerilla mar…

Brushing up on my Guerilla marketing foo, which has apparently been rebranded as Social Media.

  • Share/Bookmark

View Comments

Adding content from laptop, not my browser

I’m writing this post from my Mac’s email program. Not, importantly,from inside a browser window. I’ll submit this post by sending it toa secret e-mail address, where it will get posted automatically. Thisis cool. In an age where novels are written from cell-phone, contentsystems need to be more aware of ways people really want to interactwith their data, not just through the browser. Although I’m writingthis particular post on my laptop, I intend to write other post on myTreo 650 (I know – sooo, dated), and my via the new e-mail abilitiesof my iPod touch.I don’t think the future is posting via e-mail – I think the future ismulti-access. E-mail is great, what about IM? What about SMS? Whatabout reading on my iPod or on my Kindle?palmOne Treo 650 PDA Phone (Unlocked) Apple 16 GB iPod touch with Software UpgradeKindle: Amazon's New Wireless Reading Device

Oh yah, and then there is the whole formatting issue – but I’ll savethat for another time.

  • Share/Bookmark

View Comments

Alternative Access

I tried posting to this blog via my Treo 650 by sending an e-mail to a super secret email address. It didn’t work. I suppose that I’ll resolve the problem at some point, but regardless, the concept rocks. Imagine having a flash of insight while waiting in line for movie tickets. You whip it out, and jot down your thoughts.I suspect bi-directional communication would work better – sort of like cached Outlook access for those power travels that catch up on their e-mail while sitting on the plane.Amazon’s new Kindle calls to me – I love that it bypasses the computer altogether, yet still allows the computer to play an, optional, role.palmOne Treo 650 PDA Phone (Unlocked)Kindle: Amazon's New Wireless Reading Device

[update 2/2009: I'm writing this update from my iPhone. This is the future. Rich smart phone apps are changing everything regarding how people imterect with the data that matters. What Blackberry did for mobile e-mail, The iPhone is doing for all the other personal data]

  • Share/Bookmark

View Comments