How Baracuda Mini Apps Work
Discover the peer-to-peer event bridge, sandboxed HTML5/JS runtime environment, and decentralized Ixian network protocol behind Baracuda Mini Apps.
Did you know?
Spixi Mini Apps are just zip files containing HTML/JS. They run entirely on your device and communicate directly with your friends' devices.
Peer-to-Peer Ecology
Unlike traditional web apps that rely on central servers, Mini Apps communicate directly between users. No data farming, no tracking, just you and your contacts.
Zero Installation
Forget app stores and large downloads. Mini Apps load instantly when you need them. Share them in a chat message and start playing or collaborating immediately.
Collaborative by Design
Built from the ground up for real-time interaction. Whiteboards, games, and tools facilitate seamless collaboration between multiple users in a chat session.
Sandboxed Security
Apps run in a secure, isolated WebView container. They cannot access your private keys or files without your explicit permission via the Bridge.
System Architecture & Event Loop
How mini apps interface with the host client and Ixian P2P streaming nodes
Spixi / Baracuda Host
Native messenger runtime & key management
spixi-app-sdk.js
postMessage event bridge & RPC layer
Sandboxed HTML5 App
Lightweight client UI (Canvas, Web Audio, DOM)
Ixian P2P Stream
End-to-end encrypted packet stream
Mini App SDK Specification
Baracuda Mini Apps are static web applications packaged into lightweight `.spixi` bundles. They communicate with the host client using standard window events registered through spixi-app-sdk.js.
📦 Package Structure
app-directory/
├── appinfo.spixi # Metadata manifest (id, name, version)
├── icon.png # App icon (256x256 PNG)
└── app/
├── index.html # Entrypoint HTML document
└── js/
└── spixi-app-sdk.js # Host bridge script
appinfo.spixi Manifest Format
id=com.baracuda.spixi.my-app
name=My Mini App
version=1.0.0
description=Peer-to-peer utility application
publisher=Baracuda
category=Games
⚡ Key SDK Functions & Event Handlers
Sends a hex-encoded data payload to the active chat peer over the encrypted P2P channel.
Callback triggered when incoming data payload is received from the remote peer.
Monitors peer connectivity changes (online, offline, connected).
Requests current user wallet address, session ID, and peer details from host.
Frequently Asked Questions
Start using Spixi today!
Take control of your data and communication.
Get your Spixi for mobiles or desktops now.
