Are you updating the maps manually or is it still being updated through some web app interface?

I guess abandoning Symbian to switch to Microsoft should be considered a significant misstep, even if motivated by the then financial motives.

(Maemo, the precursor to Meego, was originally a GTK-based platform. The Symbian faction of Nokia acquired Trolltech in order to be able to advocate for Qt to be a shared development platform for both Series 60 and Maemo, which meant throwing out large parts of the existing Maemo codebase and starting again. This delayed Maemo significantly, and somewhat ignored the fact that there were basically 0 apps on Symbian that anyone cared about in the slightest)

That's not fully correct. Symbian was the leading smartphone operating system years 2000 - 2008 or so in Europe and some parts of Asia. Skype, browsers, games existed. I remember Skype offering me a refund when they discontinued the app.

I remember visiting software conferences in the US maybe 2005:ish and all the Americans had only feature phones. They seriously told me "All I want to do is call and text, I don't need anything else". The truth was that packet data coverage sucked in the US in those days.

These were Smartphones with keypad navigation (qwerty models also existed). They had packet data and the possibility to install apps, both native Symbian and Java (J2ME MIDP).

The problem was that developing for Symbian was too difficult for many programmers. Not only outside Nokia but also inside. I would claim that at least 40% of the Symbian developers did not fully understand how strings worked. Which had several types, none of which was called string and conversion between them or using the wrong one was a continuous source of bugs.

MIDP was too limited in its sandbox to build truly competitive apps.

When the iPhone came and capacitive touch started to win Nokia had nothing to offer. They had a couple of models with resisitive touch (requiring a pen or long nails), but all too little and too late.

When the Smartphone development started in the US Nokia was just obsolete. No competitive hardware and a difficult software platform. So Apple and Google conquered the world.

Depends on the time. It must have been christmas 2002 that I took my first skiing videos using the video recording app. Probably still in beta then. And I sent the app to the recipient by Email. Sending the videos went by MMS. Max size 50 KB IIRC, maybe 100 KB but I believe that came only in the next model.

Yeah, those smart phones came only with a still camera. But being able to build a video recorder show the strength of the platform. Of course there was no security model, access control or anything at the time, which made things easier.

Of course in 2010, being able to build a video recording app was no longer a competitive advantage.

Around 2003:ish Nokia was the only Symbian licensee left and they had even 3 UIs: Series 60, Series 80 and Series 90. Only Series 60 survived. Series 80 had 2 products and Series 90 one public prototype. Series 90 was the only with touch input originally. Series 60 got touch after the iPhone, but that was too late.

Yes, Symbian C++ was too difficult even inside Nokia. Productivity was very low, many products got cancelled before seeing the market and those who did were massively delayed.

That's definitely not true. I joined Symbian in 2005 and there were lots of licensees around. I think 2005/2006 were the glory years of the company.

Agree with the ugly. Well, beauty is in the eye of the beholder. Some say it was an engineering master piece of the 1990s. But it was different from everything else and it was difficult, I don't think this can be disputed.

The no good reason is not the whole truth:

* When Symbian (then called EPOC32) was developed there was no C++ compiler that supported exceptions without major problems. "Don't use them" was typical in style guides at the time. So EPOC came up with their own macro hackeries instead, which worked when used correctly. The latter was too difficult for many developers.

* Early devices had just single digits of megabytes of RAM. So 500 times less than a phone of today. More macro trickeries to save Bytes were the answer.

Porting Symbian UI to Qt meant that they could at least merge surface-level stuff and have core apps that ran on both Maemo/Meego and Symbian, then retire Symbian when no one would care or notice.

I think this is correct. It had a traditional market base but was already hopelessly noncompetitive except for old reputation and brand value (see my other comments here) and on a steep decline. Compared to iPhone and Android which were more modern and on a steep growth path.

https://gigaom.com/2009/10/23/symbian-executives-rips-into-g...

Around the official death of Windows Mobile, most of us just wanted them to launch hardware that wasn't a joke.

That's the problem with anecdotes... they only represent your very narrow window of experience while ignoring literally every other person on the planet.

> but I don't know a single person that wanted a Windows phone

I only represent a single person, and I make no claims about anyone else!

...no apps. Windows Mobile just couldn't attract quality developers to its platform. After witnessing that - I fully understood why Android went with Java (the language): there was already a deep pool of seasoned Java developers.

For instance, Apple forced people to write iPhone apps in Objective-C for years and nobody avoided the platform because of that, even buying Macs and paying 99 dollars a year for the privilege of writing and selling iOS apps.

>That's the problem with anecdotes

I'm not saying those problems affected Windows phone, but that's the association customers have with Windows as a brand due to decades of facing those problems with desktop Windows.

I like not having apps pester me for updates or pollute my notifications, when all I care about is email, websites and phonecalls (oh and offline maps, I almost forgot)

I guess I am a very boring person!

The discipline also extended to heavy sandboxing of the apps so a lot of functionality was simply unimplemetable, such as reminders for missed notifications.

But the phone worked, the UI was intiutive and responsive, and the only reason to move on, other than general phone obsolescence like the 5MP camera, was the lack of mainstream apps.

We had a brief experience with WP10 on another phone, and it seemed spiffier but less stable. WP8 was the high point.

I appreciated the consistency in design and that even the cheap devices like the 635 felt quite snappy. They also seemed a bit more coherent with update support. Yes, the no WP7->8 update path was a huge mistake, but I think by the end they were updating the OS for all WP devices (capable of being updated) centrally, rather than relying on the OEMs; the WP10 update betas I tried seemed competent enough but there was a growing sense their heart wasn't in it.

With each new generation of Windows Phone, Microsoft not only closes the gap with iOS and Android in important ways, but it also differentiates in important ways

WINDOWS PHONE 8 REVIEW

https://www.theverge.com/2012/10/29/3570494/windows-phone-8-...

On its heyday (approaching 10% in Europe), Windows Phones were seen as the alternative for those that wanted an Android alternative and didn't care about iPhone.

This is Android based on my eight years with them.

I won't argue with you on iPhone, it's a great "I just want it to work" option. And since there's no other alternative, it's what I carry today.

But Windows Mobile was a breath of competency in a market of basically all bad Google phones.

The first modern Windows Mobile phone launched in November 2015. The market of Google phones at that point in time was the Nexus 4, Nexus 5, Nexus 5X, and Nexus 6.

Now I'm not a huge fan of the Nexus 6 (though I certainly wouldn't call it "bad"), but the Nexus 4 and Nexus 5 are still to this date the best value smartphones ever released.

Everything else outside of the Chinese market has Google Play Services with root access to the system and as controlled by Google's MADA agreement with manufacturers which has already been found illegal in multiple jurisdictions across the globe.

Convention dictates that "Google phones" specifically means e.g., Nexus/Pixel devices.

Fortunately, if you're unwilling to distinguish between hardware and software, there's already a very convenient and unambiguous term for mobile devices that run Google's OS. In fact, you just used it in the same sentence!