Tagged: iphone

March 10th, 2009

2 WordPress Plugins to Mobilize Your Blog

Yesterday, I shared with you seven best practices for adding mobility to your blog, and I promised a few WordPress plugins for making your blog even more accessible with a smartphone. The two plugins I recommend tackle mobile style sheets for your iPhone, Blackberry, Android, and a plethora of other smartphones that are coming out every month by stripping out the fluff (i.e. extra-large headers, lengthy sidebars, and traditional navigation) on our regular blogs and leaving the bare reading essentials. Here we go…

MobilePress
I use this plugin to “mobilize” my sites across smartphones, for it turns my blogs into mobile sites on any hand-held device. It also gives me the option of forcing my mobile site on regular devices and allows me to decide what mobile browsers I want my blog to render in. Additionally, it comes with two style sheets but allows me to create and upload my own mobile style sheets, style sheets that could match my own site or include missing functionality that I deem important.

WPtouch: WordPress on iPhone
For the iPhone, I prefer the WPtouch plugin because it includes a lot of iPhone-specific bells and whistles. With it, you can redirect your home page, pick and choose Javascript and AJAX functions, specify colors, and select what meta information to display. The uber-cool Google functions that I love allow me to add my Adsense ID and my Analytics tracking code, so I can advertise and track my traffic on any Apple hand-held. This plugin comes with a library of icons to assign to pages and includes a Photoshop template for creating your own icons. Lastly, WPtouch works with other WordPress plugins FlickrRSS and Blip.it to show photos and videos.

I consider these two plugins essential if you intend to share your blog with readers on their mobile devices. Yesterday’s seven best practices coupled with these plugins will  get you on the road to a mobile blog that your readers will want to access no matter their location.

March 9th, 2009

7 Best Practices for Adding Mobility to Your Blog

Front face of an Apple iPhone, including default iconsI’m one of the lucky few who do not yet have a smartphone. That’s right, no iPhone, Blackberry, or Android for me; I’m stuck with an ancient brick of a phone, which is fine because in general, I hate the telephone. But Chris has an iPhone, so I’ve become quite aware of the need for mobile web sites, for I always hear his complaints when he’s on a web site that does not have a mobile version of itself. After checking the browser statistics on LifePointOzark.com and SarahJoAustin.com and noting that on both sites, access from a mobile device has increased even in the last month, I’m more than convinced that our blogs need to be “mobilized.”

So what do we do? The easy answer is to add some mobile plugins that will do all the work for you, and I will get to those plugins tomorrow, but today, let’s consider seven best practices in our everyday blogging to make them mobile friendly.

Best Practice #1: Base Your Blogging on Text
Unless you have a photo or video blog, more than likely, your blog posts are text-based, and text-based posts have smaller file sizes than those with video, photos, or graphics. Smaller file sizes allow for faster load times on a mobile device, which increases the likelihood that a reader will get to your blog and read it.

Best Practice #2: Optimize Media for the Web
If you must have video, audio, photos, or graphics in your blog posts, that’s OK. As you edit your media, find a balance between quality and file size. No, your media shouldn’t look or sound like crap, but at the same time, you shouldn’t ask your readers to wait five minutes for something to load. For images, this means using a compressed JPG format and setting the resolution to 72 dpi; for video, this might mean sacrificing HD quality; and for audio, this might mean compressing an MP3 file.

Best Practice #3: Add Title Attributes to Links
As good bloggers, we should already be adding title attributes to our links for search engine optimization, but I’ll confess, I just started being deliberate about this on SJA. For every link you add, include a title attribute that tells the reader more about the link before the reader clicks on it. Give your reader all the information they need about the link, so they can make an educated decision about whether or not to follow it.

Best Practice #4: Add Alt Attributes to Images
Assuming you’ve followed Best Practice #2 and have only essential graphics in your post, your images are already worth your readers’ time. But some readers turn off graphics to quicken load times, which means they won’t see your illustrative image. Instead they’ll see the image description from the alt attribute. Give them incentive to turn images on by adding a short but powerful description of the image (i.e. not picture of flower but pink and white stargazer lily, close-up). Think of an alt attribute this way: How would you describe the image to the blind? Whatever your answer, that should be your alt description.

Best Practice #5: Don’t Resize Images with XHTML
When you resize images with XHTML, your web page loads the full-sized imaged before resizing it to what you’ve specified. This takes precious time on a mobile device. Instead, edit your image in Photoshop, iPhoto, Picasa, or GIMP; note the dimensions; and add width and height attributes to your image tag. Both Blogger and WordPress allow you to resize images with XHTML when you add images, but don’t take them up on their offer.

Best Practice #6: Keep Text and Style Separate with CSS
This goes without saying for all the blogging platforms I’ve used, but I mention it nonetheless. If you add styles to your XHTML to specify how your text looks, your mobile browser has to “think” through all those styles at it loads the page. Plus, it increases file size. Instead, keep your blog’s structure and text in the XHTML and keep your visual specifications in CSS files. As an added bonus, you can create a mobile style sheet that will render your blog exactly as you like in your mobile device without affecting how it renders on a regular screen.

Best Practice #7: Minimize Javascript
Javascript gives our blogs functionality that is often useful on a regular screen but usually unnecessary on a mobile device. Sacrifice this functionality, and you’ll make your blog load faster by decreasing file sizes. If you don’t want to sacrifice functionality, add Javascript by linking to an external file rather than embedding the Javascript code into your XHTML. As with media, there’s some give and take with this best practice. For example, because I want to collect traffic data for my blog–wherever it is accessed–I leave my Google Analytics Javascript in my XHTML.

Faster Mobile Blog = Faster, More Accessible Blog
These seven practices will not only minimize your file sizes and speed up your blog on mobile devices, but they’ll do the same for your blog on a regular browser. Not only that, your title and alt attributes and CSS will make your blog more accessible to non-traditional readers: primarily those with visual disabilities who use screen readers or those who still have dial-up connection speeds. It’s good blogging either way.

Stay tuned tomorrow for tools that will make mobile blogging and reading easier for you and your readers.

February 16th, 2009

The Pandora’s Box of Twitter

I was a little cryptic in last night’s post about Church 2.0 and all that’s been rolling around in my head. I’m not going to give you a lot of background because that will take too long, and I want to problem solve in the here and now.

Twitter is the object of my affection, devotion, obsession right now. I use it personally and professionally. In the year or so I’ve tweeted, I’ve mostly used Twitter for posting blog updates and Facebook statuses, but in the last month or so, my use of Twitter as a networking and communicating tool has probably tripled. Maybe even quadrupled. And the more I use it, the more I see how it can be used at LifePoint.

Anthony Coppedge released his ebook The Reason Your Church Must Twitter earlier this year, and after paying the $5 to download it, I ate it up in one sitting. And then my head exploded.

In the context of the church, Twitter is excellent as a megaphone for tweeting announcements and other tidbits of information that need to get out fast. Yes, faster than email. Text message fast. In the context of LifePoint, I’m thinking multiple Twitter accounts: at least one for each key ministry, so young adults can get updates about young adult stuff and youth with youth stuff and parents with kid stuff. At LPC, that’s easily 7-10 Twitter accounts.

Twitter is also good for conversation, which is how I’ve been using it lately. If I can tell you what I need to say in 140 character or less, I’m tweeting you. Not emailing. Not texting. Not calling. I read yesterday about a church that had a “Twitter Sunday.” They encouraged the entire congregation to bring their laptops (or iPhones) and respond to the worship and sermon and service as it was happening. The tweets were displayed live on screens in the worship room. Definitely not sure if LPC is ready for that, but maybe we could start by live tweeting our services with the main ideas of the sermon and song titles and such. We could go one step further by encouraging people to ask questions about the sermon topic and feeding those to the pastor.

And speaking of the pastors (and other leadership), what a great way for them to build repoire with our people by conversing! I hear so often that people love that LifePoint is so friendly and that they’re looking for a smaller church where they can get to know everyone (including the pastor). But let’s face it, we’re at 300 people right now, and our leaders can’t have personal, one-on-one relationships with everyone. It’s just not possible, but Twitter can help.

I’m taking the worship service idea to staff meeting tomorrow. Chris is volunteering his time to live tweet during the 10:40 service since I teach the kiddos. Our lead pastor just got a BlackBerry, and I’m praying I can get him on the Twitter train.

So much to do. See how I’m overwhelmed? It’s like a Pandora’s box.  I need a plan. I guess my first task is getting the pastors on board. Then the worship experience tweeting. Then getting a few of our key leaders to tweet. Then I’ll need more web development help. Ugh. That’s another post…

P.S. And in case you’re not a Twitterer (you should be), did you know you can follow a tweeter on your cellphone without a Twitter account? Text ‘follow username’ (i.e. ‘follow sarahjoaustin’) to 40404, and you’ll get their updates. Standard text messaging rates apply, of course.

 

You need to log in to vote

The blog owner requires users to be logged in to be able to vote for this post.

Alternatively, if you do not have an account yet you can create one here.

Powered by Vote It Up