5 ms·
> Making a Windows Mobile phone only teaches you how not to make a smartphone. Not to say it's not valuable knowledge. I don't follow. Could you elaborate for
by robert_nsu 15y ago
> Making a Windows Mobile phone only teaches you how not to make a smartphone. Not to say it's not valuable knowledge.
I don't follow. Could you elaborate for me?
- cooldeal 15y agoLet me try(not the GP here). From 2002 to 2007, the only smartphones in the game were Blackberry and Windows Mobile(and Palm?). The hardware was slow and not mature and the software was slow, clunky and needed a stylus. Battery life was pretty bad, and task management sucked and ate up the battery in no time. Microsoft didn't seem to care too much about Windows Mobile and reportedly just had 5 or so people on the SDK team. The phones like the iPaq, Axim and many HTC devices saw decent success in the marketplace. The iPhone came and changed the game by leveraging advances in hardware with very good software. Thus the sneering and snark at a Windows Mobile phone in the GP post. Windows Phone is a completely different beast and seems to have learned from WM though.
- jimbobimbo 15y agoI would add that it looks like Microsoft had never considered WM to be a consumer phone: there were competing with RIM and Palm by throwing more enterprise-worth features, not caring about UX in general (other than maintaining UI styling across applications) and letting hadware vendors ship any hardware that minimally does the job and saves vendors' money. With all due respect, Apple was in an unique position: they had underserved consumer market in front of them and right hardware became available (or the processes were advanced enough to accomodate Apple's requirements in system design). BTW, ever wonder why Apple doesn't ship LTE iPhone? The hardware quality is not there yet and LTE firmwares are still work in progress.