Having to use android drivers meant having to use android HWComposer, which meant ditching X for Wayland which can use custom file descriptors, and shifting to QT5 because it supports GLES2.0 scene graph, which meant Qt Quick 2.0 had to be used.
No idea what the Sailfish UI was originally written in, but if it was Qt Widgets then very little can be reused, as its a completely different way of defining UIs.
This is the specific situation that was being referred to, and it sounds like a bucket load of work to me. Switching major frameworks is not something you can handwave away.
Which again is true for the time BEFORE the phone was out which was more than 3 years ago. What about "for tablet" update?
Which again is true for the time BEFORE the phone was out which was more than 3 years ago. What about "for tablet" update?
Yeah that was ages ago, but they were still feeling the effects of that transition in work that needed to be rectified for the tablet. This is work that would have been done without the tablet project anyway, and was started before the tablet project was even announced to the public.
But you can't just increase the DPI on a UI designed for one handed phone usage, slap it on a tablet and call it a day. Well I guess you could, but I can understand if they thought they could do better than that.
