This is the Yani changelog — every user-facing improvement, dated and written in plain words: what changed, what it fixes, and what it means for the thing you are building. Newest first, updated as we ship. Not a roadmap of promises — a record of what already landed.
Exported decks are now genuine .pptx files you can open and edit in PowerPoint, and the slide engine draws on a wider design range. The export’s temporary working files also stopped landing in your project’s output folder.
Restaurant builds now choose from six templates rather than one, and the matcher no longer trips on partial word matches — the template Yani picks fits what you actually asked for.
Research tiles now show the engine picker before the task starts, so you decide between YaniMax and YaniLite up front. Also fixed: picking YaniLite on a research task could kick off a software build instead of research.
When Yani offers landing-page directions, you now choose from options you can actually look at, instead of picking one written description over another.
Image generation for decks was failing silently and now works again, decks render on an engine that works, and the slide strip and the large preview finally agree on which deck you are looking at.
When something breaks in a preview, the error banner now names the failing component instead of hiding it in the browser’s developer tools — and each banner carries a timestamp, so a stale error cannot pass for a current one.
Enabling the database mid-project could end in “Failed to compile” — fixed. Yani also stopped building an admin panel on top of a database that was not actually there yet.
Apps Yani builds for phones now include the Dashboard button and an admin area sized for a phone screen — and it is the same backend console the web version uses, not a copy that drifts out of sync.
A ten-minute edit was spending six of those minutes re-testing pages that had not changed. Yani now re-checks what your edit touched, so small changes come back much sooner.
Asking for a change in an ongoing chat now carries the full conversation context — for builds and for slides alike. “Make it match what we discussed” works, because Yani remembers what you discussed.
Mobile previews no longer lose their connection and go dark, they remember which screen you were on across a reload, and reloading during an edit no longer blanks the running app. Edits also target the screen you are currently looking at — you do not have to say which one.
Website builds now ask about your brand — name, look, feel — before the work starts, instead of guessing and correcting after the site comes out wrong. The brand question existed in the composer but was not reaching the build; now it does.
When Yani builds a product with a database, the first thing you see is now your dashboard — the thing you will actually use — rather than a database schema card. The plan behind it is shaped around your product, not its tables.
A one-file edit no longer runs the full build suite, so quick fixes come back quickly. And describing your project in Arabic now counts as speaking Arabic — your request is handled in the language you wrote it in.
Everything above is already live — open the composer and it is yours.