Fresh ways to build, ship, and grow your apps — pulled straight from the team's commits, distilled into what it means for you.
A bug that caused apps with big data sets to silently cut off records during the build process is now caught and corrected before your app ever goes live.
When you switch between app tabs or run a search, the apps grid now dims to show it's updating — so you always know something is happening, even when your account has hundreds of apps. No more wondering if your click registered.
The Prompt Builder has moved to a more prominent spot right below the main input, so you can jump into guided app-building with one tap instead of hunting for it.
On smaller phone screens, the send button in an active agent conversation was getting cut off and pushed out of view. It now stays exactly where it belongs, no matter your screen size.
Apps built before a recent platform update can now properly restrict access to paid users — the paywall logic that newer apps already had has been backfilled to all existing apps. If your app is supposed to require a purchase to unlock content, it now works reliably regardless of when you built it.
When building apps with community or shared content features, the AI was sometimes generating a like counter on items you don't own — which would immediately fail. It now skips that correctly so your app generates cleanly the first time.
If you use the OverSkill CLI or desktop agent tools, they can now complete their login flow without being incorrectly blocked. Connections that previously failed silently during setup will now go through as expected.
When connecting your Whop store, certain payment key setups were silently failing and falling back to a lower-permission mode without telling you why. OverSkill now catches and logs the rejection instantly so the connection recovers faster and you're never left guessing.
When you connect a root domain (like yoursite.com) bought at registrars like GoDaddy, OverSkill now surfaces the correct records to enter right away — no more hunting through collapsed sections or hitting a dead end with instructions your registrar won't accept.
Apps with growing tables — think member lists, order histories, or content libraries — had several subtle display and interaction issues that only appeared once your data spilled across multiple pages. All four are now fixed.
Previously, asking the AI to edit a large file could silently fail or leave things in an inconsistent state. Now those edits are applied reliably regardless of file size.
When using AI to pull information from text-heavy images or documents, results were sometimes getting cut off before the full answer was written. This is now fixed, so extractions complete reliably every time.
A bug caused the dashboard to tell visitors they were signed in even when they weren't. This is now fixed, so logged-out users see the right experience every time.
A handful of edge cases in the checkout experience — including how promo codes locked in and how taxes displayed on the confirmation step — have been smoothed out for a cleaner, more predictable flow.
Long messages typed into text areas in generated apps were being silently cut off at 1,000 characters before saving. Your users can now type and save as much as they need.
Page 26 of 36
Browse older updates in the archive
