Speeed Reader and Twitter

A brief news update.  On August 31st, Twitter is going to be disabling the existing HTTP authentication method for logging in and tweeting using the Twitter API.  Unfortunately, all versions of Speeed Reader use this method to share articles on Twitter.  I will not be providing an update implementing the new method (OAuth) because of the difficulty and lack of time. 

As a workaround, if you use SMS to update your twitter account, you can share your articles via SMS and send them to the designated number for your Twitter account.

I apologize ahead if time for the inconvenience.

Speeed Reader v0.95

A Speeed Reader update to v0.95.  This update is specifically for those using it on Windows Mobile 6.1 Professional.  WM6.1 Pro users cannot use v1.15 because the browser doesn’t not respond to touch. Only Windows Mobile 6.5 users are able to interact with the Speeed Reader browser in v1.15. Please download v0.95 if you are a Windows Mobile 6.1 Professional user.  If you are a Windows Mobile 6.5 user and you download v0.95, you will break browser functionality.


Speeed Reader: Lessons Learned

Over the past year and some change, I have been working on a mobile application, Speeed Reader.  After many, many betas, entrance into two huge application marketplaces, bug fixes, and interactions with you, the user community I was able to learn a lot.

Speeed Reader was (a) born out of my need for a native Google Reader application, (b) born out of my need to do something innovative with my degree (was not getting, for the most part, this opportunity at the job I held during Speeed Reader’s inception), and (c) create and learn about the technologies of the mobile space (processing, data interaction, memory management).

What I Learned

Sorry if this appear to be randomly thrown together, I am typing them as I think of them:

  • Technologies: .NET Compact Framework, C++, memory management, XML parsing, HTTP protocols and connection handling, process THREADING, performance tuning, serialization, user interface design, encryption, mobile database management, error/exception handling, registry processing, software licensing and more than I cannot think of right now.  The reason why threading is in bold is that was the most important technology that put the Speeed in Speeed Reader
  • Managing a beta test team (thanks guys! your input was invaluable to Speeed Reader and me)
  • Communicating with third party vendors (Mirabyte, Microsoft, Handango, PocketGear)
  • Running a small software development shop
  • Communicating with the user community
  • Software testing on many many types of device and emulators.  Ensuring the software is stable enough for mainstream release.

Speeed Reader is the first of many software titles I am going to release under eeenno|mobile|software.  I am looking very much forward to bringing great simple to use applications to all types of platforms: Windows, Linux (downloading Ubuntu 10.04 now), Android 2.X, Windows Phone 7, and maybe WebOS (HP/Palm).

Speeed Reader v1.15 (and more!)

Here it is, Speeed Reader v1.15.  This release fixes one bug:

  • Some feeds with weird characters in the URL may not be marked as read correctly.


I have also posted all the source code for Speeed Reader v1.15 as a Google Open Source Project.  The only thing I am not able to post is the license key for the user interface controls (the DLL is posted, but is in trial mode since the license key is missing).  The controls are proprietary technology.

Project: http://code.google.com/p/speeedreader/

I ran into some issues building Speeed Reader v1.30.  I will build that and post it this weekend when I have some more time to debug.

Finally, license key for Speeed Reader: 858Bf079Jj