Is it possible to please the majority of users?

As anyone who has read this blog before will likely know, I’m working on a new iOS app called Novus, an feed reader application that is now fully driven by Google Reader. Rather than just being a client for Google Reader, Novus was engineered to use Google Reader as more of a cloud backup and really emphasise adding, removing and managing feeds within the application.

But how do I know this will make prospective users happy? Will this be a way in which they’d want to interact with Google Reader, or do they really just want a dumb client?

My idea with novus is to do as apple do. Make it powerful while keeping tasks simple to do. Hopefully this approach means the app will we both desirable to both novice and pro feed users. Building in advance sharing options that can be turned on and off by the user clearing menu space an buttons off alert sheets. Making toolbars clever. Similar to how Tapbots did this in tweetbot.

Hopefully with more developers adhering to this approach it will become possible to keep the majority of users content with your app. Let them use it how they see fit.

Farewell Steve

Here’s to the crazy ones. The misfits. The rebels. The troublemakers.

The round pegs in the square holes. The ones who see things differently.

They’re not fond of rules. And they have no respect for the status quo. You can quote them, disagree with them, glorify or vilify them. About the only thing you can’t do is ignore them. Because they change things.

They push the human race forward. And while some may see them as the crazy ones, we see genius.

Because the people who are crazy enough to think they can change the world, are the ones who do.

Steve Jobs Apple CEO April 1, 1976 – end of May 1985, September 1997 - August 24th, 2011

Posted in Uncategorized | 1 Reply

Dribbblish, a soon to be open source Dribbble API example

I was purusing @Dribbble last month looking at all the beautiful shots being listed on peoples profiles when I thought “Why is there no slideshow/view on black mode”. Naturally I used this train of thought as an excuse to hack together a quick project using @Dribbble’s (currently read-only) API.

Dribbblish was the result. Dribbblish was to me a quick fondling of the Dribbble API but it really took off with @Dribbble users getting tens of thousands of views as people tweeted their profiles being shown in Dribbblish (to view your own profile simply add your username to then end of the URL!).

But what am I going to do with Dribbblish now? Well I plan to do nothing else with it myself. Many people wanted it to be turned into a more public facing application allowing people to make theme-able @Dribbble powered portfolios. This however was never going to happen as its of my opinion that @Dribbble should be used for its original purpose, feedback on your works in progress. However I do now plan to stick the Dribbblish source up on Github over the coming days so should people really want their own Dribbblish portfolio they can, but it won’t be my fault when @Dribbble becomes a showcase site.