Earlier today I installed the WPTouch plugin, which makes WordPress blogs readable on an iPhone. It looks really nice from my perspective, however, I’m curious to know if you find this of interest/value?
To check it out, visit http://iPhoneDeveloperTips.com or http://iPhoneDevTips.com using Safari on your iPhone. The plugin offers finding content by category, searching for keywords, RSS feed, among others. The search idea has some potential to offer quick access to content if you are away from an internet connection on your development machine. However, I imagine in this case, you may also have little to no access on your iPhone.
One area that I’ve noticed where the small format of the phone will be a challenge is with the code snippets. I am using WP-Syntax to show highlighted source code, unfortunately, when viewing with WPTouch, code is truncated with no way to zoom out (even in landscape mode, much of the code does not appear in its entirety).
Either way, if you give it a try, please post a comment as I’m curious to hear what you think and if this ever comes in handy.
Comments
6 Responses to “iPhone Developer Tips from your iPhone”
Leave Comment
All Content Copyright © 2008-2012 • iOS Developer Tips, All Rights Reserved.
I think it’s great for when i click through from google reader on my iPhone… No more pan/zoom/tap required to read articles. Keep up the great work!
[Reply]
I’m always using my iPhone to read blogs, so yes — this is useful and yes I, at least, will end up making use of it.
[Reply]
I was pleasantly surprised to see that your blog implements this functionality. I’m currently browsing your blog on my iPhone actually.
[Reply]
Just a quick note: If you drag two fingers in the source code box, you can pan around and see the entire code. Not an ideal solution, as it is rather slow, but it works in a pinch.
[Reply]
This is very helpful, thanks.
[Reply]
This is a really handy plugin. I had to reinstall my wordpress so I have to add it soon but it’s a great feature for easier blog browsing from the iPhone.
[Reply]