Install from Juicery
Open Juicery and choose an app. Read its description, requirements, and available review information. AppJuice downloads and checks the package locally before asking you to install it.
The installed copy uses your own AI services and permissions. A provider connection used by the author is not included. Follow any missing-service guidance before running AI features.
Export or import a package
Use the app's sharing controls to prepare a shareable ZIP. The package carries reusable app source and configuration for installation into AppJuice.
On the receiving installation, open Import and select the ZIP. Review the inspection result and identity or replacement questions before confirming.
Review before sharing
Sharing checks the package and its capabilities. Read warnings or blocking findings, and use Builder to address required changes. Inspection helps identify problems; it is not a guarantee that an app is free of defects.
For Juicery, sign in when requested and review the proposed listing. Check the app name, description, version, and files before publishing the package.
Update a shared version
After improving an app, use the sharing flow again. Version checks can require a new version when the content has changed. Review the current scan and listing before publishing an update.
If sharing pauses for sign-in or review, continue from the displayed state. Check the published listing before assuming an upload completed.
What the recipient receives
The recipient installs an app that runs in their AppJuice environment. It may require configured AI models, service credentials, host tools, or folder access. State these requirements in the description.
Remix creates an independently editable copy. It does not give the recipient access to the author's running app or private host.
What sharing excludes
Normal app sharing excludes platform provider keys, private runtime data, sessions, and local user files. An exported app package is therefore not a complete backup.
Review app source and bundled assets before sharing. Material deliberately placed in those files can be part of the package. The package boundary does not make private information embedded in source safe to publish.