Contact details and related files

The files shown below the contact details are those sent to or received from, or authored by the contact. The contact details section increases in height to the point of only showing two rows of files if necessary.

Contacts list popover

The iPad guidelines say popovers cannot be styled so consider this aspirational.

Contacts sidebar and details split view (landscape)

Editing Contact Details

The details card slides down out of the corners and expands.

Viewing Files

The Info button at top right displays a popover listing file metadata.

Icon Sources

Some from app-bits, some from glyphish. My thanks to both.

Full 512px size:

Zipped Apple icon format (.icns), 650 KB.

The Assistant would only appear when two password input fields are detected. What to do when a site doesn’t require confirmation? Maybe check the Keychain for existing accounts at the domain and show the key icon only if none is found?

I didn’t see anything on the Snow Leopard Enhancements and Refinements page about Detectors being added anywhere but TextEdit.

A second barcode (which creates a bit of confusion) would not have to be added if the scratch-off alphanumeric code could be recognized as such using OCR. With foreknowledge of the typeface and the processing power of modern Macs, this seems technically feasible.

In case the camera is in use by another application, the Scan via iSight button is disabled and the application name is displayed.

There would have to be some conditional rules to hide the mention of optical scanning and the attendant button on Macs without a compatible camera.

Assuming this had been implemented somehow, I found the current method available in Mac applications described by Dave Mark, who learned of it from Mike Ash. The process is as follows:

1. Enter a formula in a text field such as 10/2.
2. Select the formula.
3. Press Shift-Command-8.

Easy enough, but totally invisible unless you know it’s there (not necessarily a bad thing) and yet another keyboard shortcut to remember. The fact that Script Editor pops open is also mildly surprising and irritating.

Proposed Improvements

Keeping the existing method (though not requiring Script Editor to perform the calculations) is fine for free-form text, but a design specific to number boxes would be very helpful in many applications. It reduces input repetition (a starting value is always available), application switching, and would be a great help to me as I have trouble doing math in my head. As Dan Saffer stated in his Designing Smart and Clever Applications presentation: “Do what humans have trouble doing but computers can do easily.”

1. Giving focus to a number input field displays a calculator pop-out.
   
   
2. As the user inputs a formula using the keyboard or pop-out, it is written into the field. This provides a hint to the user that they can type in formulas directly.
   
   
3. The formula is executed when the user clicks the Equals button, presses the Equals or Return or Enter key, or moves focus away from the field. The pop-out calculator disappears whenever focus moves away from the field. In the image below, Enter was pressed, moving focus back to the object in the document window.
   
   

1. iPod Settings: Party Mode off
   
   
2. Party Mode Settings: off
   
   
3. Party Mode Settings: on
   
   
   1. Wi-Fi toggle for battery conservation.
   2. Though not depicted, Brightness controls might also make sense.
   3. There is a good argument for allowing action-specific sound toggling. My thinking is that for the time the iPod is in Party Mode, it’s just a music player. You don’t want spam landing in your inbox to interrupt a jam.
   4. Enable a Passcode if you want to retain iron-fisted control.
   5. Restrictions would allow you to hide any individual app other than Music and Settings. For example, you might want to block those with personal information such as Contacts and Mail while the iPod is sitting unattended.

In my experience, iPhones users don’t offer up their devices for party music, which is understandable given that you might need your phone to take calls from guests, etc. Were a Party Mode offered on the iPhone, options to silence the ringer and send calls directly to voicemail would be useful.

For example, a band may rehearse regularly, but not on a fixed, repeating schedule that can be cleanly accommodated by a calendaring app’s recurring event interface. You want to be able to easily create an event involving the same people (your bandmates), usually at the same place (your rehearsal studio), with a varying date and duration.

Templates to the rescue.

Event Templates Pane

• Once dropped to the calendar area, the template title text is given keyboard input focus to allow renaming from the default.
• A Custom sorting option allowing the user to arrange the templates however they like might be useful. The set of templates you use may change over time as you work on different projects.
• Double-clicking a template opens the editor.
• Modifications to events created from templates do not propagate back to the template.
• Deleting a template has no effect on events created from the template.
• A menu command allows a stand-alone event to be used as the basis for a new template.

Event Template Editor

• Modifications to templates do not propagate to events created from them.
• As they exist outside of specific dates, only a default duration is set on a template.
• All other properties can be set as with normal events.

Problems

Templates would not work cleanly in Contactizer‘s All events list view. What happens when you drop a template event to the list? A title field and date/time picker could appear at the drop point. It’s still likely to be less input than creating the event from scratch.

• Shortened links remove valuable information from the address string. Maybe I can recognize the URL as being an article I’ve already read. Maybe it’s posted on a site I know to be worthless to me.
• Shortened links are hard to relocate. How do I find that link that was sent via e-mail once the page has been purged from my browser history? Of course, type “shrtng.com” in the search field of your e-mail app and then comb through the messages containing crapified URLs!

How about fixing the problem of needless character limitations instead of providing a crutch? I’ve heard the “it is a constraint that inspires creativity” line to defend the limitation. Bullshit. If you want to write succinctly, being able to write a lot does not stop you from doing so. The inverse is not true.

Given the discomfort of typing on any phone keyboard for an extended period and the burst usage patterns of mobile devices, I really don’t think there is a significant risk that removing the SMS character limit will result in people writing and sending novels via text message, thereby gobbling up carrier bandwidth and bringing down networks worldwide.

1. 1. First, a pointless welcome message that refers to the Assistant by a name different from the window title.
   2. It appears that prime marks rather than quotation marks enclose “Forward”. This typographical mistake appears throughout the Assistant.

   
   
   

2. Poorly wrapped instructional text.
   
   
3. “None” is not a sensible default for an incoming server type.
   
   
4. The server portion of the e-mail address the user input in the Identity step should be placed in the Server field.
   
   
5. 1. An automatic periodic check of 10 or 15 minutes would be a sensible default.
   2. Junk filtering on incoming messages would be a sensible default.
   3. Hiding the custom command and folder namespace settings in a progressive disclosure would cut down on the clutter.

   
   
   

6. 1. More poorly wrapped instructional text.
   2. The Assistant should take a stab at the outgoing server address based on the incoming server address.
   3. Use the incoming server username as the outgoing by default (I typed mine in).

   
   
   

7. 1. If an account name is already taken (thereby disabling the Forward button), tell me.
   2. Poorly wrapped instructional text.

   
   
   

8. Lastly, a pointless pat on the head.