App Sharing / Export / Import
Pop allows you to export the applications you create as files so they can be used on other devices or shared with other people. Likewise, applications shared by others can be easily imported into your Pop system.
The import/export feature greatly enhances Pop’s openness, collaboration capabilities, and ecosystem extensibility.
1. Why export / import applications?
✔ Share your own tools with colleagues or friends
For example, if you built a “text de‑identification tool,” you can export it and share it directly.
✔ Migrate an application to another computer
Suitable for multi-device users or system reinstalls.
✔ Team application asset management
Teams can quickly exchange tools via Export / Import.
✔ Publish to the future Pop App Store
If you plan to publish applications later, the export format will be required.
2. What is included in an exported application?
When exporting an application, Pop generates a .json file containing:
| Content | Description |
|---|---|
| Workflow | Nodes, parameters, logic, and connections |
| Layout | UI layout (components, split views, form positions…) |
| App Meta | Name, category, icon, version, creator |
| Default Input Settings | Default values, field mapping |
| Node Runtime Settings | Timeout, model selection, variables |
In other words, this JSON file is a complete snapshot of the application, ready to run after import.
3. How to export an application?
Inside App Center → My Apps, choose any application and click:
Export
The system will generate:
my-app-name.popapp.json
You can:
- Save locally
- Share with others
- Upload to cloud storage
- Store in team repositories
- Back it up to Git
This is the recommended way to back up applications.
4. How to import an application?
Click the Import App button at the top‑right of the App Center page, then choose a .popapp.json file.
Pop will:
- Parse workflow structure
- Parse layout configuration
- Create a new application entry
- Add it under “My Apps”
- Make it immediately runnable
If the imported app has a conflicting name, Pop will auto‑generate a new ID or ask you to rename it.
5. Possible issues during import
❌ 1. JSON format corrupted
File is incomplete or modified incorrectly.
➡️ Solution: Re-export or fix the JSON.
❌ 2. Required models are not configured
For example, a workflow uses GPT‑4 but OpenAI isn't configured locally.
➡️ Solution: Configure needed models in System Settings.
❌ 3. External file paths missing
Rare, but possible if nodes reference fixed file paths.
➡️ Solution: Adjust paths or input fields.
❌ 4. Pop version mismatch (future possibility)
Some workflow or layout structures may change.
➡️ Solution: Update Pop or use a compatible version.
6. Best practices for sharing apps
To make your application easier to use and spread:
✔ Write a clear description
Explain purpose, input format, and output.
✔ Design simple and intuitive input parameters
Lower the usage threshold.
✔ Provide default values
Increase first-run success rates.
✔ Use Markdown for results
Improves readability.
✔ Avoid hard-coded paths
Ensures portability.
✔ Add a nice icon to your app card
Enhances presentation.
7. Summary
Pop’s export/import functionality enables you to:
- Migrate tools between devices
- Easily share applications
- Prepare for future app marketplace release
- Save complete workflow + layout snapshots
- Build your own tool ecosystem