Just some idle chitchat and predictions, nothing serious here…
Well, it took two years after the release of a mainstream smart phone (WordPress for iOS was released in 2009, for Android in 2010). Considering that it was also during the time that mobile bandwidth usage and cost allowed for these kinds of apps, I’d say it was fairly quick. However, given that WordPress itself was 6 years old in 2009, I can see that took a while.
I doubt that.
Not because I don’t think it is possible, just that such a client would change the nature of the build system. At some point Hugo isn’t doing the heavy lifting, or the app itself isn’t that sophisticated.
See what I mean? Unless Hugo gets more pre- and post-processing hooks, a system that is adding content to a repo isn’t Hugo-specific, but it is also dependent on flat files and a build step, so I just don’t see it getting the same features as a database-backed platform, which could be considered a single system.
I haven’t seen anything close to this, and that is an issue for apps interfacing with static sites: there isn’t anything to a static site, so the tools will be built to hook into the infrastructure of the SaaS building the site. So we are going to get apps tied to a paid service.
WordPress basically suffers from a similar predicament, though the work being done on the REST API in core will open up the apps that can be used with any WP instance, and one hopes that others aside from Automattic will produce them, as the desktop apps had been in the past.
Non-scientifically, I think this is because static sites appeal to people that spend time in their $EDITOR all day anyhow. I myself am a “slow web” practitioner, and my phone is not allowed to distract me, so I am certainly not leaping at a mobile editor for static sites. Even the professional work I do in Hugo is for folks that want to change their site maybe once a quarter.
But the power and ease of Hugo and other SSGs will likely attract more diversity in users, concerning use cases and needs.