NovacraftPulsar is a tool built for the people who make mobile apps, not for the people who use them. Normally, when a team spots a typo, a broken button or a small bug in their app, fixing it means submitting a whole new version to Apple’s and Google’s app stores, waiting days for a reviewer to approve it, and then hoping each person actually taps “update”. Push that update on a weekend and the wait usually gets worse — Apple’s review in particular tends to slow down outside the working week, so a Friday-night fix can sit until Monday. Pulsar removes that wait entirely: the team sends the fix and it reaches every phone in seconds — the way a website updates for everyone the moment you change it.
Novacraft designed and built the whole product end to end: the single command a developer runs to release a change, the web dashboard where the team decides who gets it and watches it go out, the worldwide delivery network that carries the update close to each user, and the small piece of software that lives inside the app and quietly pulls the new version in.
The reason a tool like this can feel scary is the same reason it’s useful: it changes a live app in a lot of people’s hands at once. So Pulsar is built around control and undo. A release can go to 5% of users first and widen only once it looks healthy, it can be aimed at a single test account or one phone model, and if anything looks wrong it rolls back to the previous version in one click. It only ever sends the parts of the app that actually changed, so a one-word fix is a tiny download instead of the whole app again.
A command, a dashboard, a global network and a piece inside the app — designed together so a developer just pushes and it lands.
The bit a developer actually touches: one line dropped into whatever already ships their app — GitHub Actions, Bitrise, Fastlane, a plain terminal. It packages the update and hands it to Pulsar. No new process to learn.
The control room. The team stages a release, picks exactly who receives it, watches it roll out live, and rolls it back if needed — without writing any code or waiting on anyone.
Updates are stored in 300+ locations around the world, so each phone downloads from a server near it rather than one far away. Nothing for the customer to run or maintain — Pulsar operates all of it.
A small, proven piece of software inside the app that checks for a new version, downloads it quietly in the background, and swaps it in the next time the app opens. Because it speaks the established CodePush standard, there’s no risky custom code to maintain.
The whole release is three steps: build the update, send it out, and let phones pick it up on next open. A developer runs a single command; seconds later the fix is on its way to real users — no app-store submission, no review queue, no “please update” nudges.
A one-word copy fix shouldn’t make everyone re-download the entire app. Pulsar works out precisely what’s different from the version already on each phone and sends only that — often a tiny fraction of the size. Faster for users, cheaper on data, easier on slow connections.
Confidence comes from control. A release can start with a small share of users and grow as it proves healthy, or be aimed at one phone model, one app version, or even a single test account — so the team can try a change on themselves before anyone else sees it.
There are no servers for a customer to set up or babysit. Pulsar operates the delivery network, storage and edge for you, and every version is kept permanently — so rolling back to yesterday’s app is instant and safe, not a scramble.
Tell us what you're building — we reply within 8 business hours. The average response time is 1 hour.