Not sure, I was clear before: even with the FFI layer, no rooting is necessary on any device. It is supported by all suppliers. Of course, if it was only possible to run SAFE on a rooted device we would consider alternatives as that isn’t enough to reach the people we want to reach.
Technically the biggest part the launcher does is actually cross-platform in the safe_core library right now and exposed via the FFI layer. That includes the entire App-Permission-Management. So technically speaking it is “only the UI” and the stuff around the FFI that exposes the HTTP-API that isn’t portable. And when I say portable I explicitly mean the electron-app it is bundled as, because the source code itself is Javascript and NodeJS and is cross-platform: it just can’t be bundled the same way.
I have similar issues with the structure of the API as it stands right now and I am working on a headless-launcher RFC as we speak. Even though in this first step that won’t yet be fully mobile-ready (for the described use case above) it should make it possible to run the launcher on embedded and headless-devices. I hope to present a draft RFC early next week. I’d love your on input on it then!