AI has changed who builds software. If you can describe what you want, you can ship it. Send what you’ve made. We’ll add it to the apps, pay you in AI credits, and share it across our channels. Building commercially and want to bill for your add-ons? That’s the partner channel.
A prompt template. A wrapper around an existing tool. A weekend hack on Cursor or Claude. A real app. A how-to video for a marine workflow. The bar: useful on a boat, not production engineering.
Your build can run on just your own install of Shimbiri. No review, no waiting. When the same idea lands from a few captains, we lift it into the shared catalogue so every Shimbiri user gets it. AI credits scale with the reach. Your work shared across the channels we run.
Pick whichever channel you already have open. WhatsApp message, Facebook DM, LinkedIn note, email. A link, a screenshot, a description. We read everything. We say yes more than no.
Shimbiri ships every week. Builds can stay just on a captain’s own install or get lifted to the shared catalogue. The feed shows both, plus the prompts still looking for a builder.
The Chief Engineer now writes a morning briefing and sends it to the captain’s phone: battery, fuel, weather, anything that wants attention overnight. Built into the AI tier.
The site you’re reading. Three pages (Home, Apps, Boat) plus this Create page. Live preview on Netlify, iterating weekly against captain feedback.
Phone-friendly. Camera reads a QR code stuck on a locker, looks it up, tells the captain what’s in there and what’s missing. Has to work offline once installed. Reward: AI credits in proportion to the work.
Build a phone-friendly web app (PWA) that: - scans a QR code with the camera - looks up the code in a JSON file of spare parts - displays: part name, locker location, quantity remaining - has a decrement button to update count - caches the JSON so it works offline once installed Output: single index.html + service worker, no build step.
If every weather model on board is older than two weeks, the Officer refuses to give a passage briefing. No silent stale forecasts. The Captain always knows whether the briefing is real.
Pick a lat/lon. Show the next six hours of tidal current as arrows on a chart. BOM or NOAA, whichever you can wire up. Doesn’t have to be pretty. Has to be right.
Build a single-page web app that: - accepts a lat/lon (default: Moreton Bay -27.2, 153.4) - fetches tidal current forecasts from BOM or NOAA - renders direction + speed as arrow overlays on a Leaflet map - refreshes every 30 minutes Output: HTML + JS in one file, no build step.
Ask about a fault code, get the manufacturer’s procedure with the page number from the actual manual. No "the AI hallucinated my engine spec": every answer traces back to a page reference you can open and verify.
A two-minute form the outgoing watch fills in (what changed, what to watch) and the incoming watch reads on their phone before they take over. Persistent across the passage.
Build a phone-friendly web app: - a form with five fields: wind, swell, traffic, systems, "anything else" - saves to localStorage on submit - the next visitor sees the most recent submission as a "briefing" at the top - timestamped, with the contributor's name Output: single HTML file. Pretty type, fast to fill in on a wet phone.
Every new entry on this page gets posted to Shimbiri’s WhatsApp, Facebook, and LinkedIn automatically. So when you ship something, the world hears about it without us doing manual work. Sample contributions wanted.
No form. No signup. No login. A message with a link, a screenshot, or a description is enough. We’ll come back to you within a day or two.
Accepted contributions get shared across the channels above, so your work reaches the audience, not just your own corner of it.
If you’ve built one with AI in a weekend, that’s the thing. Send it.
See what’s already in the catalogue →