Skip to main content

iPhone 1.1.1 Update - Best New Feature

Apple updated the iPhone to 1.1.1 today. While most of the buzz is around the new iTunes Store, there is a small new feature that makes all the sense in the world: double-tapping the space bar will insert a "." followed by a space. So simple, yet so brilliant.

This is a classic example of taking a use case - a user wants to compose a message - watching users actually do that - and then improving upon it. Previous to this release, they would have to type a sentence, and then tap the ".?123" key to then have to type a period, then switch back. Three taps plus one more for the trailing space just for a period.

With the 1.1.1 update, all a user needs to do is hit space two times, an a period followed by a trailing space instantly appear.

How does this relate to APEX? Simple - once you design an application, you're not done. There are several improvements still to be made, none of which you will be able to identify. Watch your users use your application. You built it for them, after all!

See if they are clicking where you expect them to, and if not, you may need to re-think your design. Look for inefficiencies, such as switching between the mouse & keyboard, and try to improve upon them. Correcting small annoyances in an application will go a long way to build your credibility, if nothing else.

Good design is never correct the first time. Apple is well aware of this, and their decision to make the iPhone so bloody simple to update proves they get it.

Comments

Anonymous said…
Scott,
You're right. Apple do pay so much attention to the usability aspect of their products. I got one a few weeks ago and am throughly impressed. Even without 3g, MMS and all the other goodies I much prefer it to other phones on the market.

Unfortunately due to geographic problems, I won't be trying 1.1.1 for a little while yet ;)
September 28, 2007 at 6:20 PM
Scott said…
You best not, otherwise you will have an iBrick!

I wonder how long it will be before the new release of iTunes will require iPhone 1.1.1... :)

- Scott -
September 30, 2007 at 9:15 PM
Anonymous said…
Apple just copied the BlackBerry on this one. That double space functionality has been around for years on their devices.
October 16, 2007 at 12:05 PM
Scott said…
Apple just copied the BlackBerry on this one. That double space functionality has been around for years on their devices.

And Microsoft will eventually copy them both... :)

I think that you missed my point on this - it doesn't matter where Apple got that idea, but that they spent time to watch users use their phone, identify inefficiencies, and then correct them.

That care & dedication to their users is what I was trying to highlight as something that should carry over to all types of development - APEX and otherwise. If we all just watched how our users used our applications and then made changes to accommodate them, we'd all be better developers.

Thanks,

- Scott -
October 16, 2007 at 10:22 PM
Post a Comment

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma
76 comments
Read more

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem
5 comments
Read more

Manipulating Images with the... Database?

A recent thread on the OTN HTML DB Forum asked about how to determine the width & height of an image stored as a BLOB in an Oracle table. I mentioned in that thread that I have some code to manipulate an image stored in a BLOB column. This is particularly useful if you’re going to let users upload images, and you want to re-size them to display as a thumbnail. Thanks to Oracle interMedia , it is trivial to manipulate the width, height, and other attributes of images stored in an Oracle table. I’ve created a sample application here which demonstrates Oracle interMedia and HTML DB in action. Feel free to have a look. You can download this application from HTML DB Studio as well. Basically, this application allows you to upload images and perform an operation on the image as it is inserted into the PHOTO_CATALOG table. There are two places where some PL/SQL code is required: an After Submit process on page 2, and a procedure to display the images. Here is the PL/SQL for the After
33 comments
Read more