A mention on Developing for the iPhone and Android: The pros and cons

Jonathan Hassell has written an article for Computer Weekly on development for iOS and Android, and gives me and my book a mention: http://www.computerworld.com/s/article/9178684/Developing_for_the_iPhone_and_Android_The_pros_and_cons.

First chapters of Multimobile Development book now available on Apress Alpha program

The first ten chapters of the book are now available on the Apress Alpha program.  This is a program whereby you commit to buying the ebook at the normal price, but you receive PDFs of each of the chapters as they become available.  It’s good for readers as it gives you access to the material before the book is committed to press.  It’s good for me and Apress because it allows us to get great feedback on the book, again before it’s committed to press.  The book can be found here: http://www.apress.com/book/view/143023198x.

iPad

I’m writing is on my iPad, which I have had for a couple of days and I can confidently say that it is a *fantastic* piece of kit. I bought if off the back of an independent survey that came out with the result that only a tiny percentage (1.5%) of people regretted buying one and I can really see why.

People have been asking me how I would describe it, and on the way to work this morning I thought of one way to describe it. I think the iPad is to traditional computing devices what the mobile phone is to telephony.

The iPad brings your data one degree closer to you than is possible with traditional computing devices. Just like the mobile phone changed interpersonal communications by decreasing the virtual distance between you and people who wanted to communciate with you, the iPad (and the devices that come after them) decreases the virtual distance between you and what you own and what you want to have access to in the cloud.

Importantly, the iPad is not a big mobile phone and it’s not a small laptop – it’s a new thing that as yet doesn’t have a name.

In ten years time we’ll look back at the age before we had iPad-class devices and think “how did we manage without these” just as we wonder what we ever did before mobile phones.

New book project – Multimobile Development: Building Applications for any Smartphone

For those who don’t know, I have a new book project with Apress. Multimobile Development: Building Applications for any Smartphone is a book that takes you through how to build the *same* application for iPhone, Android, Windows Mobile, Windows Phone 7 and BlackBerry. The purpose is to create a reference guide where if you know how to do something on Platform A, you can find out easily how to do it on Platform B. (Some people who are wondering about moving from Windows Mobile 6.x to a platform other than Windows Phone may find this book particularly helpful.)

I have setup an separate site for the book, which you can find at http://www.multimobiledevelopment.com/. The book shows you how to build an application that connects to a service hosted on that server, so on that site you’ll find references to the service, and links through to Google Code that’s hosting the code used in the book. (The code for the book is published under the MPL.) Over time there will be sample chapters and other free stuff. Apress are also offering the book through their Alpha Program which gives early access to the content as it works through their sausage machine and becomes a real book. If you subscribe to the RSS feed on that site you can keep up-to-date with progress and news.

Dive into HTML5

Excellent mini-site on HTML5 features, including a library that makes detection easier Dive into HTML5.

Also… beautiful presentation.

Steve Jobs’ thoughtful/thought provoking Thoughts on Flash…

Here’s a link to an Engadget article explaining in more detail why Apple is not fussed about having Flash on the iPod/iPhone/iPad platform…
Thoughts on Flash.

Of note:

Besides the fact that Flash is closed and proprietary, has major technical drawbacks, and doesn’t support touch based devices, there is an even more important reason we do not allow Flash on iPhones, iPods and iPads. We have discussed the downsides of using Flash to play video and interactive content from websites, but Adobe also wants developers to adopt Flash to create apps that run on our mobile devices.

We know from painful experience that letting a third party layer of software come between the platform and the developer ultimately results in sub-standard apps and hinders the enhancement and progress of the platform. If developers grow dependent on third party development libraries and tools, they can only take advantage of platform enhancements if and when the third party chooses to adopt the new features. We cannot be at the mercy of a third party deciding if and when they will make our enhancements available to our developers.

This becomes even worse if the third party is supplying a cross platform development tool. The third party may not adopt enhancements from one platform unless they are available on all of their supported platforms. Hence developers only have access to the lowest common denominator set of features. Again, we cannot accept an outcome where developers are blocked from using our innovations and enhancements because they are not available on our competitor’s platforms.

Frankly, it makes sense.

For some balance, here’s some thoughts from Miguel de Icaza on the restrictions on the SDK and a ZDNet article on the same topic.

Handy list of countries in CSV format

Need to present a drop-down list of countries for a registration form? Here’s a CSV file of countries for you to enjoy. http://www.floresense.com/resc_center/?art=1360.

New OData publisher for BootFX preview available

I’ve been working on some OData components for publishing BootFX entities using the OData standards. Visit BootFX to download it.

Under the hood this uses the WCF components for working with OData messages – what we have here is a custom provider that uses the existing BootFX ORM functionality and produces OData messages.

New iPhone 4.0 SDK bars use of third-party frameworks

Matthew Fitchett (http://twitter.com/MattFitchett) points out a change in the iPhone 4.0 SDK that bars use of third-party framework layers. The Register has an article on it – iPhone 4.0 SDK bars un-Jobsian code translation. The pertinent bit seems to be this:

“Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited)”

So we already knew there was no Java on iPhone (my view on this is that it makes apps run too slowly and stops the experience fromm using an iPhone from being as gorgeously fast and slick as it is), but does this have an impact on using something like MonoTouch or other iPhone application frameworks?

Microsoft extends Action Pack to include MSDN licenses

On May 24th, Microsoft are introducing a new tier to Action Pack licensing that grants developers VS 2010 and MSDN Essentials licensing. It’s dubbed “Microsoft Action Pack Development and Design” and more details can be found here.