Mobile Web Junkie

Just before Christmas, we mobilized HowToMakeMyBlog.com by installing and configuring the Wapple Architect Mobile Plugin for WordPress.

I’ve written a much more in-depth article over there about how we did it, but here’s a bite-sized version that you can cut out and put in your wallet:
Read more

Overcoming the barriers of mobile web design and development – it’s the tagline of our blog and something that we strive towards each and every day.

We’ve given the development community some amazing tools that allow you to create some fantastic mobile sites and we’ve created plugins, components and classes that help you at every step.

Read more

Transcoding web pages into mobile web pages does not work.

There’s an ongoing debate on the subject of mobile web transcoding, so here’s our take.

Let’s be clear on our language here though. Transcoding videos for mobiles is essential and very good, but doing it to your web output is bad. Really bad.

A reliance on an automated process that takes HTML output and reformats it to mobile markup is a deluded one. Computers are really bad at recognising diverse visual patterns (that’s why we all use CAPTCHA to protect from bots) and you don’t get much more diverse than web design. If a transcoder has been taught your web layout, you’ll find yourself tied to that web design or face losing any learning invested in the system.

Read more

Konny Zsigo of the MDA recently posted an insightful article into the ‘to iPhone or not to iPhone debate.

It seems to have attracted a lot of flames. Blimey! Time for Mobile Web Junkie to dive in…

Read the  article. It’s great.

If you’re trying to make money, dump your iPhone strategy

Then the comments but in case you feel too much pain before you get as far as my comment, here it is, just for you:

Wow, what a lot of hate in the comments. I really think that a lot of you need to read back what you’ve written and see if it’s truly in the spirit of constructive debate.

I would suggest that every single flame has been posted by iPhone owners. A trait I’ve noticed is that as soon as someone jumps onto the Apple train they feel they have a fight on their hands. I guess it’s a complex caused by Microsoft constantly trumping Apple in the OS battle. Read more

Thanks to Jakob Neilson, the world is suddenly waking up to the idea that to make the web useable on mobiles you have to make the web for mobiles.

http://www.useit.com/alertbox/mobile-usability.html

We’ve been saying this for years and I wonder what took Jakob so long to discover the mobile web anyway? Maybe he was on a really long phone contract and only just got an upgrade. Or maybe his handset was so cluttered he only just found the browser.

Either way, he’s on board now and whether you subscribe to his somewhat draconian dismissal of everything pretty over everything useable you will certainly recognise the importance of such an influential character entering the affray. Read more

HTC Magic

Stop Press: The Google Android phone doesn’t support CSS.

Or so the UAProf supplied by HTC for the G1 would have you believe. We’ve got one in the office and have recently updated its browser software. Only the new user agent profile (an XML file detailing the phone capabilities) now says that it doesn’t support CSS.

The good news for users of Wapple is that the device profiling system at its heart knows that vendors sometimes make mistakes and takes that into account. Oh, and when HTC update their Uaprof so that it says it supports CSS, it’ll know and update as appropriate! Read more

We received the following comment from Jeff Miller on the ‘removing scrollbars‘ article.

“Your site doesnt even show up on any mobile phone, other than maybe an iphone. But doing a test on your site it show up very bad on other phones which most of the world use. it only scores a 3/5 on ready.mobi and its very hard to navigate on phones. Obviously you are not the mobile web junkie but the wapple (wurfl rip off hosting solution) for iphone junkie.”

Ouch. Oh well, there’s always one… The reply got kinda long but turned out to be quite a good read. So I thought it would be nice to post it as an article. Here it is: Read more

The mobile web is a great place for advertising, content, information, social experiences and fulfillment on the go. In fact, what better than the opportunity to connect with users through the device they carry around with them at all times?

Trouble is, developing for mobile browsers is hard if you don’t choose the right tools and technology to help you on the way.

If you’ve ever tried to code for the mobile web in the past (or have been lucky enough to have someone do it for you), you’ll know how hard it’s been to create a mobile site that looks great and provides a great user experience on all mobile devices.

Mobile web development is traditionally very difficult. You are not alone. In this article, I hope to explore some of the troubles encountered and then a really cool mobile publishing solution that will help you develop mobile web sites – your mobile web sites, the way you want them. I’ll also explain how you can do it quickly.

The results will optimize for EVERY mobile browser, perfectly.

Instead of having to worry about a couple of browsers as you would with a desktop browser, you’ve got different screen sizes, firmware, operators, carriers and multiple markup languages to look after – all of which meaning there’s a potential 50,000 devices to support.

That’s a staggering number. If you ever had the problem of making something work in IE6 then multiply that headache by the figure above. It’s brain-splitting to say the least.

There have been tools emerge in the past that have gone some way to helping, but now there is a new service available that has removed all of the problems and barriers to development. It’s called Wapple Architect and by the end of this article you’ll know all about it and how it’s revolutionized the entire web world.

Read more

For as long as I can remember, developing for mobile has been an absolute nightmare. To start with, there are thousands of unique handsets on thousands of operators with different browsers, firmware and capabilities. There are hundreds of different screensizes and resolutions to take care of, flash and java issues, CSS support (or lack of it) and markup languages galore. You’re not going to be able to deliver a great user experience if you can’t optimize to each and every one of these 50,000+ combinations across all the billions of handsets in the world.

Read more