Case Study: ReadWriteWeb iPhone App
When the ReadWriteWeb iPhone app was released, there was a comment on Twitter that it had taken longer than they expected to complete the development. I decided to take a look at the app to see what may have caused them issues.
Through the review I created a similar application using the TapLynx framework.
I believe that an equally usable application could have been created in greatly reduced timescales and at greatly reduced cost.
If you have any questions about aggregating your content for the iPhone, please contact us.
Navigation
ReadWriteWebApp has channels displayed on the main screen for the application for ReadWriteWeb, Enterprise, Start and Cloud, the four mains section of the site. There is also a link to the Twitter accounts of the RWW Team.
![]() ReadWriteWeb App - Main Menu |
![]() TapLynx - Main Screen |
Options for sharing – Facebook, Twitter, Instapaper and Read It Later are all available from the home screen too. These configurable options allow for easy sharing of items when reading.
The main screen is easy to navigate although it feels unfamiliar as a tab based navigation would be a more obvious choice.
In the TapLynx main screen we have included additional categories of Products and Trends as featured on the ReadWriteWeb site. The More option allows the user to configure the main screen to include Cloud, Start and Twitter if preferred.
Articles
The article listing navigation is typical and includes entries for ads and sponsors. Linking through to the article displays pages optimised for mobile with graphics displaying correctly.
Ads
As mentioned above, ads and sponsor mentions are incorporated into the article list. The current sponsor link Camera Plus Pro, is a link to the AppStore Info page which closes the ReadWriteWeb app and launches the AppStore. This could be considered out of the users control until the behaviour is learnt.
![]() ReadWriteWeb App - News |
![]() TapLynx - Article Ad |
In article ads appeared to be removed when viewed in the app. While this may enhance the experience for the user, surely the publisher is missing out on a page view, especially if the app is a success.
Performance
In the ReadWriteWeb app, the navigation between pages can be slow at times, with the selected option remaining highlighted as the next screen is displayed.
Offline Browsing
Offline browsing is not supported in ReadWriteWeb app. This is supported as standard with TapLynx.
The ReadWriteWeb app has a nice reply/retweet/follow Twitter function. All authentication is done use Twitter oAuth.
We recreated the Twitter page by grabbing the list of staff members from their Twitter page and creating a couple of Twitter Search feeds which were combined in TapLynx. The Twitter integration in TapLynx is not so solid as it relies on using the mobile version of Twitter after you’ve logged in or a simple post screen which requires your username/password once, not using oAuth.
![]() TapLynx - Tweeting |
|
![]() ReadWriteWeb app - Sharing Options |
![]() TapLynx - Sharing Options |
Search
There is no option to search in the ReadWriteWeb app. This may be linked to the lack of offline browsing. The TapLynx app has searching built-in by default.
Conclusion
The TapLynx framework offers the ability to aggregate the content from an online publication into a mobile application. The flexible design of the framework allowed configuration without coding, with excellent results.
Other publishers can save time and money with the TapLynx framework. If you have any questions about aggregating your content for the iPhone, please contact us.










