Monthly Archives: February 2010

Feedly coming to the iPhone « Building Feedly

We have been working on feedly mobile for a few months now. After a few iterations, we have reached a design which we felt had an interesting mix of fun, simplicity and speed in it. It is now time to open the door and let the community in. Here is a one minute overview of what we call %u201Cfeedly iPhone prototype 7%u2033.

In this intro video (youtube version), you will see:

  1. how to swipe through the feedly digest
  2. how to drill down into a specific article
  3. how to recommend/share an article
  4. how to tweet an article
  5. how to mark an article as read and hide it (swiping the card to the top)
  6. how to use the home option to select a specific category and feed

Although we use the same building blocks under the hood, the user experience is very different from the main feedly experience: our core design goals were/are simplicity and performance. We also wanted to make sure that we could build something that would work equally well on Android and Palm Pre.

Couple of Points. Feedly on the iPhone. Awesome! I’ve been using @feedly for about 18 months now and each time I have to use GReader on the iPhone, I feel shortchanged. The constant improvements on the service make it keep getting better and better.
My Problem is that it doesn’t work on my Mobile Device of choice: iPhone and Browser of Choice at home Camino. I understand the Camino thing is not @feedly problem, but they came up with a convoluted solution which works for Safari – why not the same for Camino?
Second, and most salient. Spot the missing ‘Smartphone’ platform on the development list. Windows Phone 7 Series better kick some serious butt for Microsoft or else what we have been predicting since 2008 comes to fruition in 2011 – more than irrelevance

Posted via web from franksting’s posterous

Feedly coming to the iPhone « Building Feedly

We have been working on feedly mobile for a few months now. After a few iterations, we have reached a design which we felt had an interesting mix of fun, simplicity and speed in it. It is now time to open the door and let the community in. Here is a one minute overview of what we call %u201Cfeedly iPhone prototype 7%u2033.

In this intro video (youtube version), you will see:

  1. how to swipe through the feedly digest
  2. how to drill down into a specific article
  3. how to recommend/share an article
  4. how to tweet an article
  5. how to mark an article as read and hide it (swiping the card to the top)
  6. how to use the home option to select a specific category and feed

Although we use the same building blocks under the hood, the user experience is very different from the main feedly experience: our core design goals were/are simplicity and performance. We also wanted to make sure that we could build something that would work equally well on Android and Palm Pre.

Couple of Points. Feedly on the iPhone. Awesome! I’ve been using @feedly for about 18 months now and each time I have to use GReader on the iPhone, I feel shortchanged. The constant improvements on the service make it keep getting better and better.

My Problem is that it doesn’t work on my Mobile Device of choice: iPhone and Browser of Choice at home Camino. I understand the Camino thing is not @feedly problem, but they came up with a convoluted solution which works for Safari – why not the same for Camino?

Second, and most salient. Spot the missing ‘Smartphone’ platform on the development list. Windows Phone 7 Series better kick some serious butt for Microsoft or else what we have been predicting since 2008 comes to fruition in 2011 – more than irrelevance

Apple and Titty apps

The cynical take on these exceptions, if you don’t buy my branding argument, is that Apple might have decided not to antagonize those companies with large, talented, corporate legal departments. 

Perhaps I’m cynical, but I think @gruber could’ve saved himself a whole lot of writing if he had just used the line I quote above.

Tim Berners-Lee weighs into the HTML5 debate

I agree with the WG chairs that these items — data and canvas — are reasonable areas of work for the group. It is appropriate for the group to publish documents in this area.
On the one hand, they elaborate areas touched on in HTML4.
On the other, these elaborations are much deeper than the features of HTML4,
but also they form separate subsystems, and these subsystems have
strong overlaps with other design areas.
It is important (a) that the design be modular; (b) that the specifications be kept modular and (c) that the communities of expertise of the respective fields (graphics and data) be involved in the design process.