Posts Tagged ‘iOS’

Clear for iPhone

Posted: February 1, 2012 in iOS, iphone
Tags: ,

Last week a came across an announcement for a new product: Clear for iPhone. From the video it appears that Clear is essentially a to-do list, but it has a very clean, minimalist interface that makes very clever use of gesture-based navigation. It caught my interest immediately, and I’m looking forward to the release of this app.

It’s already getting some buzz around the ‘net:

Ars Technica

Cult of Mac

MobileBurn

TUAW

However, as much as I’d like to take this app for a test drive, something on the company’s website really took me off guard:

It’s that whole “like” on Facebook thing. I understand that Facebook is a cheap and easy way to get some advertising. It’s a good way to do some grass roots marketing. It’s also a good way to communicate with potential customers.

The thing I don’t get is why they want me to “like” it already. There’s really nothing to like except a product announcement and a promo video. The product itself isn’t actually available yet. I WANT to like their product, and I hope I do, but I find this request for “likes” a little premature – it’s akin to asking me if I like . . . well . . . pretty much anything before you’ve let me try it. How do I know?

From watching the video, the UI is going to be pretty cool. But let me at least try it before you ask me to like it.

Where did my tech support go?

Posted: January 31, 2012 in software, tech support
Tags: ,

With the incredible growth of the iOS app store, I’ve occasionally had a need for tech support for some of the apps I use. Increasingly though, I’m finding that the quality of tech support for some iOS apps falls between ineffective and non-existent. When you stop to think about it, this can be interesting, disconcerting, annoying, and understandable – take your pick.

 

Interesting – I find it interesting, because if people want to roll out a new software product, I’d think that they also want to provide support. Good products with good support usually translate into happy users. Happy users recommend the product to their friends, and that translates into even more happy users. So when companies have bad or no tech support, it sends the message that they want to make the initial sale, and they don’t care if it breaks after you buy it.

 

Disconcerting – It’s disconcerting as well, because when I find a product I really like, I tend to use it a lot. I want to know that the company is going to be able to take the product successfully through future OS upgrades. I’d also like to know that they’re still working on the thing. After all, if they’re just going to abandon the product (and ultimately me), I want to know that as well so I can find another product that does have some support.

 

Annoying – When you find a “good” or even “okay” product, it can take a little time to get it to do what you want, integrate it into your workflow, and find the little ways to get the most out of it. When you can’t figure something out or when something just plain doesn’t work, you want to be able to get an answer from someone.

 

Understandable – Finally, the lack of good tech support is understandable. A lot of apps are free. Many cost only 99 cents. If you’re not see much (or any) return on your work, there isn’t a lot of incentive to provide support beyond that of personal satisfaction and knowing that you’ve done a good job. Additionally, many apps are rolled out by individuals rather than companies. Often software development could be just a hobby or a sideline. With other responsibilities, perhaps tech support just isn’t one of them.

 

If my bad experience with tech support had just been a one-off, I probably wouldn’t have bothered to write about it, but increasingly I’m finding this to be the rule rather than the exception. I’ve found bad tech support on apps ranging from free to $15, from almost unknown developers to well-known companies with far greater resources.

 

As I said, the quality really varies. At worst, an e-mail to technical support just floats off into the ether never to be heard from again. The next step up comes from companies who helpfully provide an immediate auto reply but never actually follow up on the problem. Then there are those who actually reply, solicit a lot of technical details from you, and then do nothing with your feedback. There are developer who do painstaking testing, replicate the problem, but tell you that unfortunately there is nothing they can do about it. And then there are those who promise that it will be fixed in the next release.

 

And somewhere out there at the far end of the spectrum, there are those developers who see the problem and either help you fix it or roll out a timely update that addresses the issue.

 

Unfortunately, those developers are few and far between – at least in my experience. When I first started working with software, there was a lot more tech support. It wasn’t always good, but – given enough time – they usually got the problem solved. And at least they knew how to return a phone call or an e-mail message.