All talk about Steve Jobs can sometimes be quite tiring. It is however hard to dismiss his insight into the domain in which he was working. Here is a speech from 1983, in which it is clear that he had a firm grasp on what was about to come. He gets many things wrong, such as the idea of the hand held iPad kind of device within the 1980s (it took 20 more years). But it is extremely interesting to listen to many of the things he got right.
I especially like how he wants computers to beautiful and that industrial designers must pay attention to the computer industry to start working towards more beautiful artifacts, and more beautiful experiences. He says that these things (the computers) will inevitable be all around us, in our home and in our offices, and so we now (1983) have the time to make sure they are beautiful. Unfortunately the IBM desktops kind of took over for a long time and we had those gray boring things for a long long time. But I think we can see how that is changing with companies putting more efforts into doing beautiful devices (computers, mobile phones, tablets). If only they would have started doing that already in 1983…
Listen to it here.
Forbes has an article on how to choose between mobile web and native apps. It has a simple overview of pros and cons of the two, and what intermediate versions there are. Their claim is that it is more complicated than two ends of a spectrum, but you can choose in between. Most interestingly is what they name a dedicated web app
Dedicated web app, which is a mobile web site tailored to a specific platform or form factor, like the LinkedIn web app which was designed for Android and iOS, but not for other smartphones or feature phones.
as opposed to a generic mobile app “which are mobile web sites designed to match every web-enabled phone, like the Wikipedia mobile page.”. I have definitely gone for the dedicated web app more times than the generic mobile web app.
I agree in principle with their end points, which state that you should build whatever solution you decide on, on the data. Create an API for the data, and build the app to use the API. This is really just good development style, but can definitely help when building mobile (web) apps if you need to try different solutions later on. As some people advocate “web first, native second” (e.g. this guy), having the API and data in place, you have laid the ground work.