This week has been less than satisfying from a developer’s point of view, and I’ve found myself stuck hanging out with my good buddies Outlook, Word and Excel a lot more than I’d have liked However despite that I’ve still managed to pick up a few useful bits of mobile development information.
Allow me to share, if you will.
jQuery mobile – resizing to landscape mode doesn’t work properly. Basically when rotating the device, the windows new size wasn’t quite correct. While it felt like a minor annoyance at first, it quickly became pretty clear it was going to be a real pain if it wasn’t fixed! Luckily it’s a simple fix – it’s just a matter of changing the viewport meta tag.
From what’s recommended in the jQuery mobile documentation:
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="viewport" content="initial-scale=1, maximum-scale=1">
As is often the case I found this information on Stackoverflow – it’s interesting that the original post is regarding beta 1, and this is still an issue in beta 3. I’d really have expected more people to notice and mention this.
jQuery Mobile – large performance delays when viewing certain pages. I was viewing ‘detail’ pages and experiencing large delays that didn’t really make a lot of sense. I can’t claim to have 100% identified what was causing this, but I’ve made the delays go away which is good enough for now.
In my app (which is ASP.NET MVC3 using Razor) I was setting some ViewBag properties that were updating header values (SEO metatags basically), and jQuery mobile wasn’t happy about this at all. I removed the changes to those header values and all was well. I’ve since gone on to re-write that page to use partial views and AJAX updates so it’s even less of an issue now, but I’m still interested in going back at some point and doing some profiling to see why changing those head values can make such a huge difference (an additional 40+ seconds to page load times).
iOS Boilerplate Application - this is a base template for iOS apps, inspired by the HTML5 boilerplate. It’s a convenient way to get up and running with native app development and includes support for HTTP Requests, Image management, UITableView and calls, maps and locations, and more.
Appcelerator Developer Blog – Forging Titanium Episode 6 is a useful read for anyone working with Appcelerator. The series is getting into some good detail about ways to structure apps in Titanium, and is worth a read for Appcelerator developers. Also if you’re looking for some guidance on structure and layout then Titanium application structure – learning from Tweetanium is well worth a read too.