App Design Philosophy

If you’ve been following my last few blog posts, you know I’m currently in full-on app design mode (the idea, the map, the wireframes). So in between the time spent actually working on it, and between the client work, I’m spending a lot of time just thinking.

Thinking about a few philosophical ideas when it comes to designing a successful app. These points speak more to particular type of app I’m working on (team relationship management app), not necessarily all apps in general. But some things may relate to yours or someone else’s (maybe not). OK, enough blabber… Here’s what’s been on my mind:

Focus on solving one main problem, not many related problems

Not a new concept really, but I still see so many apps—particularly those in the project management space—try to tackle too many different things. “It’s a personal to-do list, invoicing, proposals, collaboration, cloud storage, and CRM all in one!” No, it’s not. It’s probably a great invoicing tool, with mediocre other functions that I personally don’t care about (a.k.a. “bloat”).

Now, this isn’t to say that solving one main problem involves having only one function. Several functions/features can be combined to solve one larger problem. For example, Basecamp offers a solution for having a centralized team project management hub. It’s focused solely on managing active projects nothing else. But it has several functions: Messages, To-Do lists, Milestones, Writeboards, and document storage. Is it trying to do too much? No, because these are all integral functions to the primary focus: Project Management.

The app I’m designing focuses solely on team building / business expansion. The associated functions include: Organizing a distributed team, managing applicants, hiring new people, and managing business growth.

Consider how your users interact with non-users

Since the app I’m designing is targeted primarily at business owners who team up with other independent contractors, my goal is to make it as useful as possible for the business owner (our user) and as non-intrusive as possible for the independent contractors (not our user). Those independent contractors have their own systems and apps they prefer to use. They don’t want to be burdened with changing their workflow to fit one client’s system. What I’m trying to do with this app is have clearly defined areas for private personal use of the app, with optional areas for community/interaction.

Stick to real pain points, don’t reach

I’m a strong believer that a sign of a winning app idea is one that you’d personally use or rather you personally need. My business is currently in that growth phase and I’m finding it harder and harder to organize and grow my network. I personally need this app. In fact, even if it never gets released or sold, I’d still want to use it for myself.

So defining my own pain points is the main driver behind my creative process for this app. What I’ve noticed is that it’s easy to stray from these pain points and reach for new ones, essentially trying to create pain points that don’t really exist.

When you find yourself reaching for a new problem to solve, it’s a good sign to start slashing features and come back to your core idea, your solution to your real problem.

Interested to hear what you think… now back to work