There may be times you’ve downloaded a cool application with a new kind of user interface component, and you’ve wondered: how was it built? One great example of this is the rotary wheel, used by ConvertBot and other applications as a way for users to select options from a menu. This component is intuitive to use because it resembles many similar controls we use in real life to make choices. For example:

• A ship’s wheel allows the captain to choose the direction of travel.
• To set the volume of your stereo, you use a rotary knob.
• You might also remember that we used to call people using rotary dial telephones.

Such shared knowledge allows us to recognize the “possible uses” of a rotary wheel, even when it’s a virtual wheel.
Note: A perceived use of an object is also called an affordance, a concept used in such fields as psychology, design, and artificial intelligence.
In brief, a rotary wheel is meant to be spun. Just as with hardware wheels, touchscreen wheels can be configured in many ways. For example, we might include stop points (as in the rotary dial on a phone), ignore initial taps in a given zone, allow just one direction of rotation, etc.
As you may have deduced, this tutorial will show you how to build an intuitive rotating wheel interface. You’ll then be able to integrate this component into your iOS apps and let other people wonder how you built it ;]

Read the rest on raywenderlich.com

This article from Business Insider got me started. Since I have to time to address potential fanboy arguments let’s go this way. For each time you think I am a fanboy I’ll think of you one of the following:

- troll
- user who has time to loose with lower quality devices/experiences
- user who likes to accumulate stress

Right now that Eric Schmit is promising that Android will soon beat iOS (whatever is the meaning of beating in this context), Android’s throat is getting more and more exposed. I can’t provide evidence but I started to feel a while ago that Android has found his way: more and more devices released and much buzz around the topic. But I always got in mind a few key aspects:

1. Fragmentation: it is not easy at all to build an homogeneous experience across many different devices
2. Too much fanfare about the number of devices activated per millisecond
3. Nobody has ever revealed how many dollars has Google shared with developers

While the second is mainly related to marketing and the too much diffused tendency to reveal meaningless numbers, as a UX designer, developer and entrepreneur I am pretty sensitive to points #1 and #3. The first is pretty a technical reason: developers have to write more code and carry more stress with respect to iOS. The third point is pretty a mystery to me: Apple is known to be pretty secretive, especially when prototyping, but is proud to reveal key numbers to attract more on their platform. Rhetoric questions for developers/entrepreneurs: which market would you dive in? the one where you know the current volume or the one you don’t know anything about? While reflecting on this please don’t fall into the childish thought that “more devices more potential buyers”, unless you are a rookie. Just consider that you are making money by selling applications, and a higher number of devices does not imply a higher number of sales. The key value is the “willingness to buy”, and the internet is full of articles supporting the idea that iOS users are more prone to buy applications than androiders.

Getting back to the main point of this article the new announcement from Samsung, that won’t allow upgrades to the new version of the OS on old devices, is really exposing Android’s throat to attacks. While it was relatively easy to copy (umm … take inspiration from) iOS and its ecosystem, now I think that Android has reached a pretty unsolvable issue: the one of upgrades. People who bought an iPhone 3gs (released in June 2009) can still happily use it today with iOS5 and the iCloud. Can you find a similar example in the Android world? I doubt so. The reason is exquisitely technical: relatively young devices have not enough hardware power to run new versions of Android OS. It is just a physical limit, and I think there is nothing to discuss. My opinion is that it is due to lack of vision. One of the few upgradeable devices is the Galaxy S2, because it is a flagship product, and preventing an update on that would mean users migrating to other devices in a hurry.
I am not a fan of Microsoft but if you bought the first model of Windows Phone you can still happily run the latest version of the OS on that. This means being on track.

Besides technical reasons I think that there is an issue related to the approach. While it was possible to “decouple” hardware and software on the desktop (and Microsoft has built his empire on that) this is much less doable in the mobile world, where hardware power is limited.

Here are a few suggestions for Google, makers and users.

Makers

HTC, Samsung and colleagues should follow Amazon approach. The only way to attack a well established market are a few. You can work on:

• the best product
• the best solution
• the best price

Amazon, to attack the tablet market, is betting on the best price. I don’t see a simpler way for competitors to undermine Apple’s iOS ecosystem. Building the best product or solution would take a lot of time.

Google

Google should close the gates, reorganize all the code to be more tightly coupled with hardware. They should put a lot of effort in rendering, demanding that (when possible) to the hardware. They should also devise crystalline rules about installation and updates. In 2012 I should not connect my phone to a computer to update the OS and I should not be forced to buy a new device to have the latest version of the OS. The recent acquisition of Motorola
is going toward that direction. If I were HTC or Samsung I’d be a bit worried, for I suspect new versions of Android will be super optimized for Motorola hardware. That’s the only solution I see for Android to resurrect.

Users

In the current situation, my suggestion is to go cheap. If you buy a $500 Android phone which is not OS-upgradeable it is not easy for you to afford a new purchase. If you have bought a $200 one, you have saved $300 (with respect to an iOS device) and you can think of using that money to buy a new model in one year.
Of course it is not easy to spot which models are upgradeable before you buy them (see crystalline rules above).
In general, we are told that a Google-approved Nexus device, should be eligible for upgrades (my addition: provided that hardware is powerful enough). So if you really like to buy an Android phone/tablet I strongly suggest to stick with those models or buy the new ones which will be released by Motorola in 2012.

Conclusion

While Google and friends are just chasing the highest number of activations per day, exposing his throat to competitors’ weapons, Microsoft and Apple are pointing on good experience, simplifying data migration and assuring compatibility with old models.

I’d like to conclude with a set of questions:

• where is all the “freedom” that Android supporters claim?
• do you realize that openness and (supposed) freedom, in the long run, are more costly than “closed-source” competitor solutions?
• do you see all the ifs you are going to face buying an android powered device?
• do you know that all this is due to a business model

?

• Not convinced yet? Have a look at this graph.

He moves like Steve Jobs and his attitude is inspiring as well.

This is an excerpt from my chapter on iCloud included in iOS5 by tutorials.

We all have “stuff” we use on our iPhones and iPads regularly like documents, pictures, videos, emails, calendars, music, and address books. But how many times have you tried to quickly open a document and realized “argh, I have it saved onto another device”?
Well, with the new iCloud feature in iOS 5, that is problem of the past!
iCloud is a service that helps you synchronize your data across devices. It is a set of central servers which store your documents, and make the latest version available to every device/app compatible with iCloud (iPhone, iPod, iPad, Mac, or even PC).
In this tutorial, we’ll investigate iCloud by implementing a set of simple applications which interact with cloud servers to read, write and edit documents. In the process, you’ll learn about the new UIDocument class, querying iCloud for files, autosaving, and much more!
Note to get the most out of this tutorial, you will need two physical iOS devices running iOS 5 for testing, such as an iPhone and an iPad. The simulator does not currently have iCloud support.

Under the Hood

Before we begin, let’s talk about how iCloud works. In iOS each application has its data stored in a local directory, and each app can only access data in its own directory. This prevents apps from reading or modifying data from other apps (although there are some alternate methods of transferring data between apps built into the OS). iCloud allows you to upload your local data to central servers on the net, and receive updates from other devices. The replication of content across different devices is achieved by means of a continuous background process (daemon) which detects changes to a resource (document) and uploads them to the central storage.
This works real-time and enables another interesting feature: notifications. For example, whenever there is a conflict about a document, the application can be aware of that and you can implement a resolution policy.
If you ever tried to create something like this with your own apps, you know there are several major challenges implementing this:

• Conflict resolution. What happens if you modify a document on your iPhone, and modify the same document on your iPad at the same time? You somehow have to reconcile these changes. iCloud allows you to break your documents into chunks to prevent many merge conflicts from being a problem (because if you change chunk A on device 1, and chunk B on device 2, since chunk A and B are different you can just combine them). For cases when it truly is a problem, it allows you as a developer fine-grained control over how to handle the problem (and you can always ask the user what they would like to do).
• Background management. iOS apps only have limited access to running tasks in the background, but keeping your documents up-to-date is something you want to always be doing. The good news is since iCloud synchronization is running in a background daemon, it’s always active!
• Network bandwidth costs. Continuously pushing documents between devices can take a lot of network bandwidth. As mentioned above, iCloud helps reduce the costs by breaking each document into chunks. When you first create a document, every chunk is copied to the cloud. When subsequent changes are detected only the chunks affected are uploaded to the cloud, to minimize the usage of bandwidth and processing. A further optimization is based on a peer-to-peer solution. That happens when two devices are connected to the same iCloud account and the same wireless network. In this case data take a shortcut and move directly between devices.

The mechanisms described so far are enabled by a smart management of metadata like file name, size, modification date, version etc. This metadata is pushed to the cloud, and iCloud uses this information to determine what needs to be pulled down to each device.
Note that devices pull data from the cloud when “appropriate”. The meaning of this depends on the OS and platform. For example an iPhone has much less power and “battery dependency” than an iMac plugged into a wall. In this case iOS might decide to notify just the presence of a new file, without downloading it, whereas Mac OS X might start the download immediately after the notification.
The important aspect is that an app is always aware of the existence of a new file, or changes to an already existing file, and through an API the developer is free to implement the synchronization policy. In essence the API allows an app to know the “situation” on iCloud even if the files are not yet local, leaving the developer free to choose whether (and when) to download an updated version.

Read the rest on raywenderlich.com

I will try to argue why the current discussion on open vs closed source is a non sense for the final user. Honestly I am try trying to figure out why Apple and its steersman sometimes bring the topic up. They usually care of design. I am not the first to say that Apple is a design company. There is no mention of technical specs in Job’s presentations. Devices have to the be disassembled to find out components. So I wonder why Jobs mentioned this “low level” topic about closed vs open source. Probably it is a marketing technique.

My first (and almost only) claim is that end users care of experience. I am trying to put myself in their shoes. When they enter a shop they want to buy something that works and that they like. When they ask a friend a suggestion about a phone/tablet, they wanna know whether it works, it is fast/reliable. Probably the only low level detail that is worth asking is the memory, but not in terms of gigabytes. A common user usually asks: “how many pictures/songs I can put in there?” If you are a developer this is non sense to you, but I mentioned it exactly to give you an idea of how far we are from the open/close source topic.

MacOSX is based on an open source kernel. Try asking an Apple maniac why he bought a Mac. I am pretty sure the answer won’t be “because the source code of the kernel is available”.
Experience is a relation between a user and a tool. A great user experience can be achieved regardless of the availability of the source code. In this case Apple looks (and just looks) as a contradiction: MacOSX has success and it is partly based on open source code. The iPhone has success and it is based on closed source code.
Another example: Ubuntu. The adoption of Linux on the desktop is growing and it started growing when somebody put effort on its user experience. Remember how was KDE 2? Check it out know.
So the question “is open better?” has many answers. If I need to set up a fast, secure and reliable server to build my next killer project the answer is “yes”. Yes, because I can check the code to detect flaws, to tune it to my hardware, etc. In this case I am not an end-user, I am a developer or a system administrator. If I am a masseuse from Brooklyn and I want a smart tool to make calls, browse the web, listen to my music and take pictures the answer to “is open better?” is “I don’t know/care”. I will never try to recompile the OS, at most I can install some application, so I am not really interested if my geeky neighbor can change the behavior of my phone.

Now a few words about open. I am an insider and I like open source. I have released some opensource code and I use opensource code almost daily. In my career I have learned that there is “Open” and “open”. This is a very inspiring post about this difference. In general open does not mean that everybody can get in. The door of a hotel is usually open but there is a concierge. If you are staying there you can get in, otherwise you can’t. The Linux kernel repository has a well-know doorman: you can write patches/modifications but if he does not approve them you are not in. Open is a very overrated term, sometimes used to make a good impression. Like when there is a party but you cannot get in, let’s say you can stare at an open door/window.
Moreover, those who can get it are not allowed to do whatever they want. For example the Android OS has a governance philosophy, so you have to adhere to a compatibility program. This is great. I am sure that anarchy would not lead anywhere. My only objection is: the focus of that document is just on compatibility, not experience. You are not allowed to change the scheduling of threds as you like, but you can do whatever you want with user experience!
I am not saying that to achieve a great user experience you have to close your source. I am saying that “do whatever you want” is not a good strategy to achieve it. To build user experience you need focus, vision, discipline, measurements.
For example one of the features of experience is recognizability (the ability to recognize an object and its intended usage). I am not saying that the iPhone and iTunes store are the only/best way to distribute applications. I am saying that they are consistent and recognizable. So after a few interactions I get familiar with them and if Apple does not revolutionize their interface I will feel familiar also with next versions. Can we say the same of the Android ecosystem?

My conclusion is: an open source product is better only when it can compete with the user experience of its closed source counterpart.

A few days ago, as many developers, I got the following message from Apple.

I think it is a good step towards developers. A small one, but towards. The feed, publicly available, includes tips about submission and general news. For example, iTunes connect will be down from Dec 23rd to 28th. An encouraging news is that “92% of applications are being approved within 14 days”. Although this is far from the dream of many developers I think it proves positive attitude in cultivating the relationship with the creators of iPhone applications.

In the meantime, acceptance policies are sweetening.

You probably know Adobe is working to enable the development of iPhone applications on the Flash IDE. Yep, your imagination is correct: open Flash, write actionscript code, follow some step and end up with an iPhone application. The feature has been announced during the last Adobe Max conference. The great evangelist Lee Brimelow realized a video that illustrates how you can build iPhone applications through Flash CS5, which will be available as a beta by the end of the year. Though still limited (e.g. you don’t have a real simulator) the idea looks promising. I will continue to develop iPhone applications the “old way” but I’ll stay tuned for new developments on CS5. If you didn’t watch the video yet, go!

After six months of iPhone these are my reflections, in the form of “The iPhone is a …”

Time saver

The only thing to complete your daily todo list is to wait for an email and redirect it to someonelse? Go to the beach, play volley and in the pause between one set and the other check the email and reply/redirect accordingly.

Angryness preventer

You have to go to pick your girlfriend up. You’d really like to check some more news or finish reading a blog post, but you agreed to be at her place at 9 pm. You are on time, she is late. With no iPhone you’d probably feel angry. Grab your iphone out of the pocket and finish checking news. Stumbled upon something interesting? Use Read It Later.

Boredom preventer

Bored to wait at the bus stop? Nobody to talk to and the bus is late? Open one of the tons of applications and play with it. Side effect: might loose the bus.

Good guide

Looking for a bank around you? a bar? Open up Around Me and find what you need.
Got lost. Open the Maps application and follow the path to get to your destination.

Cool to program

Tired of virtual machined/garbage collected languages? Looking for some new development platform to expand your knowledge and your business? Have a look at the iPhone. I bought it because of development purposed (top secret at the moment) and I ended up with the iPhone as my daily technological companion. There is plenty of tutorials, books, forums and open source code to learn from.

Probably everything I described above can be experienced with some other 3G enabled phone, except the cool-to-programness, which is what I appreciate mostly at the moment.

Flash running on the android platform? Yes. Flash was already been demonstrated as running on android. Now Bsquare has been charged to make the porting of the flash technology to the android platform. I started the study of the iphone sdk a while ago, and so did many flexers/actionscripters. But this news makes me mumble. I like learning new languages/frameworks a priori but I probably will have to set a preference: android or iphone?

I have set up a poll here. State your opinion!

I started developing in Flash, doing websites. I then moved to Flash mobile (before the introduction of flite) and developed a mobile guide for a research project. When Flex was presented I didn’t dive into it, because I was busy with other projects and languages. When Adobe Air (introduced as Apollo) was released I started experimenting again. When I heard of the iphone I thought: “This is the platform of the future!”. But I felt disappointed when Steve confessed he didn’t like Flash on the iphone. Now I am simply thinking:

• isn’t iphone running Safari? Yes
• isn’t Safari based on webkit? Yes
• aren’t Adobe Air application partly running on webkit? Yes, if developed in javascript/html.

So? I think it is not far the moment that ad Adobe Air application will run on the iPhone.