Comment by oriolid

The problem with Symbian was not the usability but the developer experience.

SDK available only for Windows and really awkward to install and use? Check. Pre-11 C++ but without exceptions and something called cleanup stack and ELeave macro instead? Check. Ok, a whole periodic table of string classes instead of std::string (which would still have been terrible because it was before C++11)? Check. GUI API that was designed for a Psion handheld (Uikon) and implementation for Psions (Eikon) and Series 60 UI implementation (Avkon) piled on top of that? Check. App architecture that doesn't really have a concept of standalone app but works on the idea that apps are views and controllers that handle files? Check. What about making every single phone model slightly different so that apps are not portable between Symbian phones by default but you have to actually test and port with every model? Check. And there was a lot more at deeper technical level that I never had to reach.

I understand that the developer experience was better for the last Symbian versions but at that point it was already late, iOS and Android were taking over and Symbian had a reputation to fix.

My definitive memory of Symbian development having a lunch at a Nokia cafeteria, a week after starting the job and all the dreams about having a computer in your pocket that could run anything as long at it didn't need huge amounts of CPU power, memory or screen area crushed, and complaining with a friend who was in similar situation. An older engineer had heard us, told us that we don't know anything about how bad S60 is and continued with a hour-long rant that as far as I know was all pure facts.