Publish on Cricap
Build and publish
a Cricap miniapp.
By Cricap · Updated · Contact the team
Miniapps run inside Cricap on desktop and mobile web. Users discover them through shared posts and can share them to their own timeline.
Open Developer Portal1. Set up your developer profile
Sign in with your existing Cricap account. Provide a contact email; a developer display name is optional. You will use this portal to track submissions and review feedback.
2. Build and test your miniapp
Host your app at an HTTPS URL. It must work in an iframe on mobile and desktop, with a compact embedded layout and an expanded layout. Provide a separate review build URL for the Cricap team to test.
The current Trends host supports readiness, unavailable, expand, sign-in and Share to Cricap messages. Use the adapter below for this interface. The existing Cricap SDK also documents other platform APIs; they are not automatically available in Trends. Do not depend on wallet, score submission or user-token methods in this host.
Download the Trends bridge adapter and include it in your app:
<script type="module">
import { createTrendsBridge } from './trends-bridge.js';
const bridge = createTrendsBridge();
// Fetch and render your content first.
bridge.ready();
document.querySelector('#share').onclick = () => bridge.share();
document.querySelector('#expand').onclick = () => bridge.expand();
// If the content cannot be shown: bridge.unavailable();
</script>The host supplies your assigned app ID, a positive numeric content ID, the display mode and its origin in the URL. Keep content IDs stable so old posts continue to open the same content. A standalone app can use content ID 1 for its main experience.
Your frame must allow embedding by Cricap web origins. Keep app secrets on your server. The host does not pass Cricap member credentials to external frames; protect private data on your own backend. Cricap access restrictions control whether the frame can open inside Cricap.
3. Submit for review
Submit the app name, description, category, review and production URLs, privacy policy and support email. An icon URL is optional. The portal assigns your app ID. Add that ID to your integration, then keep your review build available while the team checks it.
Reviewers check loading, mobile layout, content access, sharing and your privacy information. If changes are needed, the portal shows feedback and lets you revise and resubmit. Published apps cannot be silently replaced through the submission form; contact the team to arrange a reviewed update.
4. Choose a release with the Cricap team
Approved for general access. When staff enable store visibility, your app appears in the production Cricap Miniapp Store immediately.
Testing with selected Cricap accounts. The app is not listed publicly.
A limited pilot with selected Cricap accounts. The app is not listed publicly.
Only Cricap staff set approval, release labels, test accounts and store visibility. Users outside the selected accounts see “Miniapp unavailable.” Hiding a Live app from the store preserves shared access; disabling it blocks access inside Cricap.
5. Share your launch
Use Share to Cricap inside your miniapp to attach it to a new Trends post. Any Cricap member who can access it can share it too. Direct miniapp links and notification links continue to work without a header entrance.
Submit your miniapp