4 ms·
Was this around the time Microsoft kept switching what "windows phone" was? I remember that the one friend who got into it loved it, and then they released some
by bombcar 2y ago
Was this around the time Microsoft kept switching what "windows phone" was? I remember that the one friend who got into it loved it, and then they released something completely incompatible and he abandoned the platform.
- masom 2y agoYes... If I remember we were aiming for the newly released "Windows 8"-based Phone OS, and the previous version was fully incompatible with it so all apps had to be redone. Tiles were the new thing to build for.
- jandrese 2y agoMicrosoft tried to do the same thing on the Desktop side too, but on the desktop they were forced to keep the backwards compatibility in place so it didn't finish off the platform the way it did on the Phone side. Amusingly Microsoft is still trying to make the walled garden happen. Lots of cheap Windows laptops and Desktops ship in what is called "Windows S" mode where only Microsoft Store apps are allowed to run. But again because PC owners don't abide that kind of bullcrap they also have to supply a way to tear down the walls (it's surprisingly easy, albeit permanent: just download and run a free app from the Windows store) if you want to use the machine in a normal way.
- inquirerGeneral 2y ago[dead]
- jorvi 2y agoIf memory serves, it was a custom kernel and OS, then a semi-custom kernel with a few OS components shared with Windows 8, and then the Windows 10 'core' kernel (same as on the Xbox One?) with many shared OS components. At each step they left the majority of devices behind. What was equally worse was the triple (quadruple?) switch of app frameworks. If I remember correctly it was a dotnet abomination, then ?? then WPF and finally Xamarin. Good luck convincing your platform 3rd party developers to entirely relearn and rebuild their app four times over in the span of a few years. Interestingly enough, Windows Phone itself was far ahead of it's time. Buttersmooth UI, flat UI, built-in global and app dark modes, all in the early 2010s.
- 7thaccount 2y agoButtersmooth UI is how I'd describe it too. I loved the themes at the time too.
- robertlagrant 2y agoIt was incredibly smooth. The Windows Phone 7 browser was also very smooth compared to the iPhone/Android browsers of the time. Some miracles worked somewhere. Also the keyboard was incredibly good.
- kernal 2y agoI had a few Windows phones, and butter isn't a word I'd ever use to describe the performance of the UI. Heck, I wouldn't even use the word margarine to describe my experience with it.
- 7thaccount 2y agoOut of curiosity...why did you have several? Were they budget models?
- delusional 2y agoAs I recall it, calling Windows Phone "buttery smooth" is quite an overstatement. I remember it looking drab dull and cheap at the time.
- rescbr 2y agoI had two Lumia flagship phones - Lumia 800 with Windows Phone 7 and Lumia 930 with Windows Phone 8 (which I later upgraded to 10). Both look and feel awesome, not cheap at all. At the time, Microsoft were paying developers to port apps to Windows Phone. There were developers who took the effort to make their app look native, and I'd say Windows Phone 7 had the best UX to this day.
- kernal 2y agoIt's hard to take someone seriously when they overexaggerate like that. Windows phone was never butter or margarine smooth.
- 7thaccount 2y agoI had the original iPhone, then swapped it for a flagship android and hated it. I tried Windows Phone out a few years later and loved it and had two of them over the years. Some apps didn't exist for it and that sucked, but the OS was snappy and something different that I really liked. The Nokia windows phones were great. I knew it was doomed though as when I got them from the carrier, I was apparently like the only person despite it having its own wall at the brick and mortar store lol. I still miss it.
- cbozeman 2y agoMy cousin says the same thing... 25 year IT veteran. Early adopter for almost all new tech. He says his 1000-whatever Lumia phone was one of the best phones he ever owned. I know it ran Windows Phone OS, and I remember playing with it a bit.
- startupsfail 2y agoI remember having a Windows PDA when I was in college, and developing a bit on top of Windows M. It was a reasonable platform. But Microsoft was too greedy with their licensing schemes and demanding too much adaptation from the hardware and chip manufacturers. You’d think they would adapt their OS and drivers, but no, you had to tape out new silicon for them. So they’ve lost the mobile OS market. It feels like something like this may happen with the AI OS now. They are pushing hardware manufacturers to conform to their standards while Linux is adapting to what is available and working already.
- int_19h 2y agoWindows Phone had pretty much nothing in common with WinCE/WinMo PDAs that preceded it, at least from user and app developer perspective.
- 7thaccount 2y agoI think this hurt Windows Phone a lot as a lot of people thought it was just the PDA interface on a smart phone.
- asveikau 2y ago2009 and earlier: Windows Mobile was based on WinCE. The UI was garbage but the innards were pretty functional, and there was desktop-like multitasking. Unpopular opinion: they should have just done a UI refresh of that thing and moved it to an NT kernel. There were a lot of cool third party hacks on this platform. 2010: Windows Phone 7 was still WinCE, but they removed full access to WinCE APIs, and got rid of PC style multitasking. They had a new UI framework for first party apps. Then for third party apps they had a port of Silverlight that imitated the new UI style. The latter had really terrible performance. They had to base this release on WinCE because the NT kernel port to ARM wasn't ready yet. Blocking access to "good" APIs could be seen as a way to ensure app compatibility for the next release. 2012: Windows Phone 8 had the NT kernel. Also, windows 8 and windows RT shipped. But the silverlight-inspired UI framework of Windows 8 was different from the Silverlight fork from Phone 7. So you had yet another UI framework rewrite to cope with.
- jandrese 2y agoAt the time Steve Jobs was putting his foot down against allowing Flash on the iPhone because the performance was so pants, Microsoft was going all in on Silverlight which had exactly the same problem.
- scarface_74 2y agoThat’s a popular misconception. The first iPhone had a 400Mhz processor and 128MB of RAM. It was so resource constrained that you couldn’t put a picture on your home screen because it would have taken too much memory. It could barely run Safari. If you scrolled too fast, you would see checker boxes while trying to render the screen. When Flash did finally come to mobile on Android, it required a 1Ghz processor and 1GB RAM. The first iPhone with those specs didn’t come out until 2011. Even then on Android, Flash ran horribly and killed your battery. I had a high end Android phone on Sprint back then.
- asveikau 2y agoIt's easy to forget how popular flash was in that decade. A lot of us found it annoying on desktops too. Not to mention Linux, where we'd deal with binary blobs that were pretty unstable, not because we liked it but because you needed it to interact with the world. I have not so pleasant memories of having a few different versions of their plugin and I'd try to figure out which one worked for a given website, symlink the right one and restart the browser. And that was the way to watch videos online...