Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2018-12-09 05:23:58 +0300

The future of the browser in SFOS

This question asks how the current bad situation of all native browsers in SFOS can or should be handled and describes the view on it of a returning user.

Current situation: (boring to most as we all know it)

All native browsers are unusable for more than browsing on really basic websites. It is generally very slow. The chance of some of the following problems is high (ordered by their bad impact ascending)

  • many elements are rendered wrong or are hidden.
  • sites showing a none passable error page pointing you to updated your browser.
  • the website does not load at all.
  • the website does not load at all and the whole OS restarts or has to be restarted.

I can just browse on like 50% of my regular websites without a major bad impact. I can't visit some at all and one crashes the whole OS every time.

My history with SFOS to understand my point of view (Just skip; boring for all ;))

I started with Jolla #1. Had much fun as well as bad headaches. For some time it was OK. But because I had problems with the hardware I tried to change to the Intex phone but didn't get it through the customs and never saw any hardware or refund (I knew the risk. I arranged with it). Out of reasons I don't know in detail anymore I changed to iOS. The biggest was obviously the lack of trustable hardware at that point.
I followed the progress of SFOS from a far position here and there.

Now it's already years later I bought Sailfish X and a Sony Xperia X two weeks ago and since then I use it as my only smartphone on daily basis.
I actively read the recent questions, blog posts and the log of the last Sailfish OS open source collaboration. I'll reference that later.

What is / could be the solution we are heading to ?

Most interesting for me was the log of the last Sailfish OS open source collaboration. The browser was the biggest topic which was a nice sign. As much as I liked the positive acting of many community developers I felt daunted about the conclusion of the Jolla statements or those statements that are missing.

Here to tell my current knowledge what will happen:

  • Jolla currently sticks to the gecko engine in the official browser.
  • A QT update to most likely version 5.9 will come at a unknown date. Hopefully in the next few month. It may come with a usable QTWebEngine but no one knows.

... Directly followed by the alarming questions I have:

  • I miss a major sign that the officials know that a mobile OS needs a usable native browser. The only statement I see is ... the browser is open source. Everyone can improve it.
  • If the official browser sticks to the gecko engine there seems to me the need of big improvements in this part.
  • I see a still fairly motivated webcat developer who could add an unofficial usable browser or even help on the stock browser with some changed sign. Where is the needed official help/groundwork. Wouldn't that be a win-win situation?

Conclusion

Regarding Jolla-Together and blog posts I wondered the most about the recent lack of transparency, enthusiastic mood, vehemence to a browser and browser-component everyone is able to use and new users won't be discouraged immediately. Both from community and officials.

The future of the browser in SFOS

This question asks how the current bad situation of all native browsers in SFOS can or should be handled and describes the view on it of a returning user.

Current situation: (boring to most as we all know it)

All native browsers are unusable for more than browsing on really basic websites. It is generally very slow. The chance of some of the following problems is high (ordered by their bad impact ascending)

  • many elements are rendered wrong or are hidden.
  • sites showing a none passable error page pointing you to updated your browser.
  • the website does not load at all.
  • the website does not load at all and the whole OS restarts or has to be restarted.

I can just browse on like 50% of my regular websites without a major bad impact. I can't visit some at all and one crashes the whole OS every time.

My history with SFOS to understand my point of view (Just skip; boring for all ;))

I started with Jolla #1. Had much fun as well as bad headaches. For some time it was OK. But because I had problems with the hardware I tried to change to the Intex phone but didn't get it through the customs and never saw any hardware or refund (I knew the risk. I arranged with it). Out of reasons I don't know in detail anymore I changed to iOS. The biggest was obviously the lack of trustable hardware at that point.
I followed the progress of SFOS from a far position here and there.

Now it's already years later I bought Sailfish X and a Sony Xperia X two weeks ago and since then I use it as my only smartphone on daily basis.
I actively read the recent questions, blog posts and the log of the last Sailfish OS open source collaboration. I'll reference that later.

What is / could be the solution we are heading to ?

Most interesting for me was the log of the last Sailfish OS open source collaboration. The browser was the biggest topic which was a nice sign. As much as I liked the positive acting of many community developers I felt daunted about the conclusion of the Jolla statements or those statements that are missing.

Here to tell my current knowledge what will happen:

  • Jolla currently sticks to the gecko engine in the official browser.
  • A QT update to most likely version 5.9 will come at a unknown date. Hopefully in the next few month. It may come with a usable QTWebEngine but no one knows.

... Directly followed by the alarming questions I have:

  • I miss a major sign that the officials know that a mobile OS needs a usable native browser. The only statement I see is ... the browser is open source. Everyone can improve it.
  • If the official browser sticks to the gecko engine there seems to me the need of big improvements in this part.
  • I see a still fairly motivated webcat developer who could add an unofficial usable browser or even help on the stock browser with some changed sign. Where is the needed official help/groundwork. Wouldn't that be a win-win situation?

Conclusion

Regarding Jolla-Together and blog posts I wondered the most about the recent lack of transparency, enthusiastic mood, vehemence to a browser and browser-component everyone is able to use and new users won't be discouraged immediately. Both from community and officials.