Registro de mudancas

Connecting a custom domain to a Cloud app now explains itself better - especially for root domains.

• Squarespace DNS is now recognized. If your domain runs on Squarespace

nameservers, the wizard shows the exact ALIAS record their panel expects.

• The wizard names your DNS provider. When a root domain can't point at

Playcode, the wizard now tells you which DNS service it detected and which nameservers prove it - no more guessing whether the check is right. This especially helps domains bought at Google Domains and moved to Squarespace, which often still run on Google's nameservers behind the scenes.

• Unknown providers are never a dead end. If we can't identify your DNS

host, the wizard now shows the ALIAS record to try instead of blocking you - and still recommends the www address that works everywhere.

Browser projects now have Checkpoints - restore points you can save at any moment and return to instantly.

• Save a restore point. Open the project menu and choose **Checkpoint

history, then New checkpoint**. It captures all your files exactly as they are - instantly, without using any credits.

• Name your checkpoints. Rename any checkpoint so "Before the redesign"

is easier to find than a date.

• Restore instantly - and undo it. Restoring puts every file back the way

it was. Playcode saves a safety checkpoint of your current state first, so a restore is never a one-way door. The page does not reload, and your chats stay exactly where they are.

• Publish keeps you covered. Every publish automatically saves a

checkpoint of what went live, so you can always get back to a published state.

You can keep up to 20 checkpoints per project. At the limit, Playcode asks before making room by deleting the oldest one.

Want to explore two directions side by side? Use Duplicate project - the copy gets its own files, chats, and published site.

Email on Playcode Cloud grows up: on paid plans, your app's emails are now really delivered - not just captured in the Mailbox.

• Deliver to verified recipients. Your own address works instantly (you

verified it when you signed up), and your team's addresses too. Add anyone else in Settings > Email - they get a verification link, and once they click it your app can reach their real inbox.

• Honest status on every message. Mailbox messages now show their real

fate: Sending, Delivered, Bounced, or Marked as spam - with the reason, so debugging "the email didn't arrive" takes one glance instead of guesswork.

• New apps send from day one. A fresh full-stack app now emails a

welcome message to its very first registered user - so you see your mail pipeline working before writing a single line of email code.

• Fair pricing. Emails to yourself and your team are always free.

Beyond your plan's monthly allowance, delivery is pay-as-you-go with credits - priced in line with the leading email APIs.

Free projects keep the full capture experience: every email lands in the Mailbox, rendered with working links, ready to test end to end.

Playcode can now build presentations, and it asks one question first: do you want a link you open in the browser and present fullscreen, or a .pptx file you download and edit? They are different things, so it settles that before writing a single slide.

The .pptx is a real one. Actual text boxes you can click and retype, real tables, real speaker notes, charts that carry their own data sheet. It opens in PowerPoint, Keynote and Google Slides, and Cyrillic, Japanese and emoji come out exactly as they went in. This is not a picture of a slide wrapped in a PowerPoint file, which is what most "export to PPTX" buttons hand you.

The more interesting version is a deck generator. Describe the presentation you rebuild every cycle - the monthly client report, the one-pager per prospect, the board update - and Playcode builds you an app that produces it. Your spreadsheet, database or CRM export goes in; finished decks come out, one or two hundred of them, on brand every time because the brand is written into the code. Next month you press the button instead of rebuilding the deck.

A few things worth knowing:

• Generating files needs a full-stack app, since a static site has nowhere to write one. Playcode will offer to set that up.
• Ask for both and you get both from one source: a browser deck to present from, plus a download. Change a slide once and both update.
• Slides use fonts that exist on the machine opening them, so nothing reflows into a substitute when you send the file to a client.

Playcode can now make audio. Ask for it in plain words and you get a file, hosted and ready to use in your project:

• Music - a background bed at an exact length. Ask for eighteen seconds and it ends on the eighteenth second, which is most of why a video reads as finished rather than assembled.
• Sound effects - short one-shots. A click, a coin, a whoosh, a notification.
• Voiceover - narration read aloud, for a walkthrough, a tutorial or an explainer.

It works in any project. A browser game can have its own soundtrack and its own effects without becoming a full-stack app, because the audio is generated on Playcode's side and your project simply receives the finished file.

Everything comes back already levelled to the loudness social platforms and browsers expect, so a clip does not arrive twice as quiet as everything else on the page and need fixing by hand.

Audio uses credits from your balance, priced by what each piece actually costs to make - so a one-second sound effect costs about what a one-second sound effect should, and you are not buying a bundle to get one noise.

On iPhone, tapping certain inputs - the answer boxes when the AI asks you a question, search fields, rename boxes - zoomed the page in. That part is normal iOS behavior for small text fields. What was not normal is that you could not get back: pinching to zoom out did nothing almost everywhere, so the app stayed magnified and unusable until you reloaded.

Two things were wrong, and both are fixed.

• Pinch-to-zoom works again across the app. The chat transcript, the message box, and every editor panel were opting out of the browser's zoom gesture - only the top bar still responded to a pinch. They now allow it, while keeping the scrolling and drag behavior they were reaching for.
• Fields no longer trigger the zoom in the first place. Text you type into is now sized so iOS leaves the page alone on focus, on phones and tablets. It is also simply easier to read.

Nothing changes on desktop.

Full-stack apps on Playcode Cloud now send email out of the box - no provider signup, no API token, no DNS setup.

• Zero configuration. Password resets, verification emails, order

notifications: your app's email code just works. Playcode provisions the credentials automatically when your app is created.

• The Mailbox panel. Every email your app sends appears in the editor's

new Mailbox panel within seconds - rendered exactly as a recipient would see it, with working links. Trigger a password reset, click the link in the captured email, and complete the flow end to end without leaving Playcode.

• Safe by default. New apps run in capture mode: emails are stored and

shown to you, never delivered to real inboxes - so you can build and test freely. Real delivery to your users is coming next.

• API keys, done properly. The new Settings > API keys page manages

named keys with per-key permissions (send-only or full access), shown once at creation and revocable individually - and Settings > Email shows your sending mode and usage at a glance. A stuck loop that sends the same email over and over is paused automatically; one click resumes it.

Signing up is now one continuous flow instead of a series of popups.

• One setup journey. Answer a couple of quick questions right where you

signed up - no second dialog appearing later, no design jumps.

• Team setups land right. If you choose With my team, your company

workspace is created during setup and your first project is created inside it - together with your welcome credits. Working solo? Everything stays neatly in your personal workspace.

• Your work survives sign-in. Building something before signing up?

Your edits and drafts now survive signing in with GitHub or Microsoft, and your project is saved to your new account exactly as you left it.

Clicking Logout could quietly do nothing: the menu closed, no error appeared, and you were still signed in. It happened when Playcode was open in more than one tab - the sign-out waited on a local data cleanup that a second tab was holding, and then waited forever.

Sign-out no longer waits for anything. Your session ends the moment you click Logout, and the local cleanup happens afterwards where it cannot get in the way.

Two related gaps closed at the same time:

• Every tab. Logging out in one tab now ends the session in your other Playcode tabs too, instead of leaving them signed in with a session that no longer exists. A tab holding unsaved work stays put rather than reloading over it.
• Only your own data. Signing out used to try to clear the cached data of every account that had used the browser. It now clears only yours, so signing out of one account no longer disturbs another on a shared computer.

"How do I share projects with my team?" is the question we get most, so the Help Center now answers all of it - no support chat required:

• How to share a project - invite people by email

with Viewer, Editor, or Admin roles, manage the Access list, and use the public link. Fully rewritten for the current Share tab.

• Workspaces and teams - the difference

between your Personal workspace and a team workspace, inviting members, and granting access to a whole team at once.

• Roles and permissions - the full

reference: what each role can do in projects and workspaces, how overlapping access combines, and how invitations work.

• Move a project to another workspace -

bring existing projects into your new team workspace. Chats, data, and history travel with them; nothing needs to be recreated.

The Learn about sharing link in the editor's Share tab now lands on the rewritten guide.