What we need to figure out(doesn't seem to be part of mini-app standards yet):
- How does Servo install a mini-app?
- process the manifest,
- load the file,
- store data and assets somewhere,
- add a native icon to enable loading the app.
- How dos Servo load a mini-app?
- as part of navigation
- intercept the network
- caching and offline(SW cache storage?)
- Advanced features
- notifications
- updates
- Other system, or super-app, integration
- elephant in the room: AI
- Figure certain architectural features
- example: the "JS thread for business logic".
- usecases. Example: "a more performant cross platform web app. (like react native)"
- For a web engine, at what level does a super-app come in?
- Is the super app the embdder, or the engine(probably the embedder)
- Can you just embed a webview, or do you need the engine to support the usecase?
Note: progressive web apps do the above using web standards(servive workers and so on).
A few links:
- MiniApp APIs Gap Analysis
- https://globaldigitalcollaboration.org/agenda?day=2025-07-02(filter down to payments use case)
- AI agents running mini-apps to do stuff idea: https://medium.com/@polyglot_factotum/web-based-ai-agent-system-5f103006c4a2
- Slides by Thomas at Web Engine Hackfest and his presentation.