Before FamilyManager 3.0 came out, I asked myself an uncomfortable question: is the app really simple? Not “fairly clear”, but as simple as you expect an Apple app to be. I clicked through the app, counted, and wrote the results down in an audit. The result was sobering and useful at the same time.

What the audit showed

The core actions were already fine. Checking off a task takes one tap, creating a task or an event takes three. Everything around them was complicated:

These are the figures from 23 October, measured on the development build at the time. They come from the audit, which I followed through in the simulator and in the code.

My yardstick was Apple’s interface guidelines. One sentence from them hit me in particular: “Minimize the number of settings you offer.” In FamilyManager I had tended to answer “should this be configurable?” with yes.

What I decided

My advice to myself was: mostly leave things out and hide things, build hardly anything new. For 3.0 I settled on this:

What I deliberately kept

An audit gives suggestions, but not every one belongs in the app. Two things I deliberately did not cut:

Both decisions are now on my “do not suggest again” list. Leaving things out is only a strength if you can also say no to your own cutting suggestions.

One sentence instead of three

The language of the app was an issue too. The app spoke in three places with three different sentences. “Your family. Organised.” and “More time for what really matters.” are gone. One sentence remains:

Abhaken statt Nachhaken. (In English: “Checked off. Not chased.”)

Below it: “You don’t have to think of everything alone.” It should say the core of the app in one breath.

What I take from this

Simplicity rarely comes from a beautiful design for me. It comes from counting: screens, switches, words. Once the number is on the table, cutting gets easy.