Because opening an app is one click on the app grid. Two at worst if it’s in a folder.
Opening a webpage is more involved. And whether you like it or not, people want stuff to be easy.
You can either accommodate them or walk around telling everyone how it sucks that people are like that nowadays. I generally try to be productive instead of complaining, hence me adhering to what the user expects.
Webpages can be pinned to grid, no problem. If what you were proposing was a good wiki refresh, and just a dummy app in store being a link to it, i would not be complaining.
Do not let it discourage you. Being against your app is likely just an isolated opinion.
An app is much easier to use on a tiny phone screen than any web page. I love Sailfish for the user experience, for example, how easy it is to navigate with one hand. That is why many will always prefer a native app, tightly integrated into the UI concepts of the OS, over a web page that is often not optimized for such. Plus, the SFOS browser is often useless anyway.
I would also say that app is more convenient for new user, in most convenient situation the app would even be pre-installed or pinned in Jolla store. Also good point from @pherjung that open-sourcing the Tutorial app could be beneficial!
Both the sources and the texts of this app are already open source and on github. See the very first post.
Open sourcing the Jolla Tutorial app would be better, of course. But who would want to wait for Jolla…
The benefit of an app in this case is that it showcases Sailfish in the Sailfish interface. A tutorial is better the closer it is to how you actually interact with the interface.
If you are going to add a section to your app about this forum, would it be stupid to consider adding a short list of some of the most common abbreviations used here and their meanings, such as SFOS, AAS, FSO, TJC, etc.?
I did a little bit of work on the app and it’s visually and functionally close to where I want it to be. The only thing missing is handling of links to other documents and some app translation stuff.
Afterwards I’ll consider the app good enough for version 1 and focus mostly on the content.
When you download it, unzip it and simply create a new folder with the language tag in the docs folder, for example fr. Every folder can have an index.md file which is kind of a default page which should serve as an introduction.