Linked by Thom Holwerda on Wed 19th Sep 2012 16:08 UTC
PDAs, Cellphones, Wireless "High Tech Computer (HTC) has grown up with Microsoft, from the old HTC-built iPAQ's running on Microsoft's Pocket PC operating system, to the Orange SPV - Microsoft's first Windows smartphone. The Taiwanese company has always been a loyal aid to the software giant, but lately that close relationship has started to feel a little dated. HTC's investment in Android and its Sense user interface has taken precedent over its initial work with Windows Mobile, and the company's Windows Phone flagships have been impressive, but overshadowed by Nokia's colorful Lumia range and partnership with Microsoft. That all appears to be changing though." HTC announced some good-looking Windows Phone 8 phones (ugh) today, but from my personal experience of owning several devices from both brands for over a decade, Nokia has the edge on quality. Good to see a serious commitment to WP8 though - we wouldn't want the Android dominance to continue.
Thread beginning with comment 535785
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

I kinda get what alfman is saying dude. On one hand in that last thread you were basically saying you should never use html5 apps when you can write a native app. Yet here you are endorsing using a web app for something as critical as managing your files.

Packaging an html5 application in something like phonegap allows a web app to have much better integration with the native system. So allows one to write an html5 application that will allow easy manipulation of cloud based storage that integrates with the native os and can run on multiple platforms. Which apparently you are now apparently a proponent of even though in the last thread you clearly stated a complete and total disdain for any html5 based app because native development is better.

Am I missing something here. How do you explain these seemingly opposing views?

Reply Parent Score: 3

Nelson Member since:

When a user goes to a website, they expect one. They know it isn't an app.

When a user downloads an app from an app store, they don't expect a website. They expect a native app. Something that integrates, feels, and performs natively.

You quickly go onto uncanny alley where something kind of looks right, but isn't, so it becomes less pleasant to use. Basically, in this scenario the user takes a back seat to convenience.

Now, I welcome you to read my comments in their entirety in full context and you'll see I make this same point which helps reconcile these two views.

Facebook is an example. They serve native apps on iOS, Android, and Windows Phone. However, for everywhere else, there's a least common denominator website. The reach is there, and the experience is preserved because the underlying service is platform agnostic.

Let's say I'm speaking about SkyDrive to make things simple. Sure, there are SkyDrive apps for the platforms. Sure, they feel nice and native, as they should. However, there's also a SkyDrive website for everyone else.

Its possible for me to say that an HTML website is a good idea for reach, and not contradict my very specific views that HTML isn't suitable for something that's packaged as an app and sold on an app store.

I think I've been as clear as possible with this comment this time around, so I expect you'll understand my point now.

Reply Parent Score: 3