Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "ColdFusion"
channel.
-
15
-
2
-
2
-
Windows Phone was very much emphasizing form over function. For example, the idea of making those on-screen “tiles” display actual content, rather than just being static icons, seems like a good one, until you see how they implemented it. I remember during a demo by a Nokia exec, you would see things like the email icon dancing around in a distracting way, even when there were no new messages to display. This kind of useless “noise” in the UI is just going to put people off.
And there were too many limitations in the actual OS. For example, Windows Phone 7 didn’t allow apps to access the actual file system, whereas you could do this on Android. Windows Phone 8 I think relaxed this restriction, but then the app build process was done in a strange way which involved accessing a Microsoft server, so you couldn’t actually do builds just on your own facilities.
There were hardware limitations, too. Windows Phone 7 could only run on a single core, while Windows Phone 8 required dual-core hardware. This when the newest versions of Android were available on devices with anything from one to four cores.
Also I remember HTC (the king of the Android heap at the time) brought out it’s “One” series of models, in both Android and Windows Phone versions. The Android versions had hardware features beyond those available in Windows Phone. It’s clear the only reason HTC was bothering with Windows Phone was because Microsoft was paying it to do so.
1
-
1
-
1
-
1
-
1
-
1
-
1