I’m not as technical as I wish. So you need to read this by Dropbox: The (not so) hidden cost of sharing code between iOS and Android.
For me it’s obvious. When an app doesn’t respect the accessibility settings I have on the phone, I get angry. (Of course, ‘angry’ is my go-to, so take that for what it’s worth.)
I have this blood pressure hardware device that’s great, but the software… it sucks. I can’t read it without my glasses even though I’ve set my iPhone to have text quite large.
I think it’s really important to fit into the customer’s world, and not remind the customer that they’re stepping out of their world to use your product. But, I’m not technical enough to express the development process behind that.
And that’s why I like this Dropbox post. Many large companies have moved from “write once, run anywhere” to native development teams, but this post is the first that addresses the practical day-to-day reasons.
I think we’re in such a different world from “windows and a browser” and most companies haven’t figured it out yet. We really are early in the mobile computing world when it comes to the experience we can expect as customers.