The rollApp approach (from my limited view of it) seems to add another layer of complexity, basically trying to redirect the desktop gui to a web interface. More of a tack-on blob to get existing linux apps to show on the web.
Building a RESTful API (which is basically a set of ideas on how to interface to any resource on the web), would provide a clean interface to our back-end Gramps database. Through these APIs, one could build a modern web app or mobile app calling the same back-end APIs. It also provides a way to safely deliver the data in the database without having each user directly connect to the database.
It’s more of a design change from a monolith desktop app to more of a micro-service approach, where the data may be stored securely in one place, and the client/app is being run in another place (tablet, phone, laptop, web, etc).
Another thread talking about GUI design would fit nicely into this project. I’m new to open source, but from my perspective this whole endeavor would require some project management so it all heads in the direction that 80% of us want it to head in.
To me, this would be broken into maybe 3 parts - the web GUI (design), the API design, and the back-end (core) GRAMPS database. We’d want to be able to leverage as much from the existing core Gramps as possible, but I think most of it is GUI/front-end work, that would need to be totally re-done. (and thus, we’d want to really think about what a new UX design might look like).