Feature Request: Capacitor Export Option for iOS & Android Apps

Feature Requests
1

What do you want to see in Hype?

A built-in Capacitor export option (or guided integration) that can take a Hype document and generate ready-to-build iOS (Xcode) and Android (Android Studio) projects using Capacitor.

The goal would be to:

• Export the Hype project as web assets

• Automatically generate the Capacitor wrapper project (with sensible defaults)

• Provide a simple workflow for syncing or rebuilding when the Hype project changes

This would enable creators to ship Hype-powered experiences as installable apps, with access to native capabilities via plugins.

Have you found a workaround for this problem?

Yes, but it’s currently too manual and fragile:

• Exporting HTML from Hype and then setting up Capacitor separately (config, platforms)

• Maintaining build/sync steps and folder structure manually

• Repeating the process for every update or across multiple projects

This breaks the fast iteration workflow that makes Hype so enjoyable.

Are there examples of other apps with this feature? Or, have you seen examples of this elsewhere on the web? (Please include a URL)

There are different approaches and framework-based solutions to package web content as native apps, including some no-code and low-code builders.

One related example is PubCoder, which uses its own viewer-based approach to package interactive HTML content (including Hype exports) for distribution. There are already known workflows and guides for using Hype exports inside PubCoder, which demonstrates a similar need from a different angle.

This request is not about replicating another tool, but about offering a more direct and streamlined path within Hype itself.

How high of a priority is this for you?

[ x ] Nice to Have
[ ] Important
[ ] Can't use Hype without it

Hype already excels at producing lightweight interactive web content, and a Capacitor export option would make it much easier to deliver those experiences as native apps without changing the core workflow.

1 Like
2

Thanks for this request as well!

Generally we've demured from having some sort of app export within the app. This is for a variety of reasons (many business/cost centric unfortunately).

But that said I coincidentally was doing some unrelated work with Capacitor earlier this week, and actually came across pretty impressed (especially in conjunction with ionic). So at least some of the knowledge is there.

I think the approach we'd prefer to go is a way for others to develop plugin and export flows with Hype, so solutions for any particular framework can be maintained independently. Right now Hype supports Export Scripts which have a lot of possibilities for crafting a Capacitor output. It might be difficult to make a complete solution this way (especially with some of the syncing/updating) but could get you some of the way there in the export.

1 Like
3

Stepping back a bit, I think this also connects to a broader opportunity for Hype.

Hype already feels very strong and well-focused as it is, and with clearer positioning it could continue to grow within specific domains — such as instructional design and education, advertising and marketing, web interaction, and even lightweight no-code / low-code application development.

In that context, a plugin and template–driven ecosystem (rather than adding everything to the core) seems like a natural and sustainable direction. Export flows, integrations, and higher-level patterns could live there, maintained independently and driven by real use cases.

A marketplace-style structure would also help solve the motivation and sustainability question for more advanced workflows, while keeping Hype itself focused, lightweight, and opinionated in a good way.

Just sharing this as a broader framing — I think Hype is already in a great place, and an ecosystem layer like this could amplify that strength without diluting its core identity.

Of course, this perspective is shaped by my own current use cases and the way I work with Hype; you naturally have a broader view of the product’s long-term direction and constraints.

2 Likes