SketchUp activePreferences
Changelog
We ship aggressively, but this page keeps only what matters to architects: visible improvements, fixes and beta decisions you can feel in the product.
The private beta form now uses the project's native flow from end to end, removing a hydration mismatch without changing cost, confirmation or report behaviour.
The page opens without a browser mismatch
The action still requires confirmation of 1 credit while removing a client-side island that existed only for the button, reducing the page's hydration surface.
The private beta form now uses the project's native flow from end to end, removing a hydration mismatch without changing cost, confirmation or report behaviour.
The page opens without a browser mismatch
The action still requires confirmation of 1 credit while removing a client-side island that existed only for the button, reducing the page's hydration surface.
The private beta organises priorities, client questions and presentation order inside each project's real context before the next render spend.
Decisions stay with the project
The new plan turns the brief, scenes and production status into a short action sequence without opening a generic chat or separating analysis from the work.
Cost and autonomy remain controlled
Each plan requires explicit confirmation of 1 credit, saves the report for later and never edits scenes, starts renders or publishes content on its own.
Dashboard, auditor, billing, account and credit history now keep secondary actions comfortable on phones while preserving a professional desktop density.
Operational links respect 44 px targets
Queues, summaries, policies, return links and account shortcuts get complete mobile touch areas without looking oversized on larger screens.
Visual QA understands labelled checkboxes
Validation now measures the associated label's clickable area, avoiding false alerts for accessible controls while retaining warnings for genuinely small checkboxes.
Filters, scene selection and render actions now provide larger touch targets on phones while preserving the desktop's operational density.
Gallery filters get a complete touch area
Status and project filters now provide 44 px targets on mobile, reducing mistakes when switching through a real library with many items.
Scene controls no longer depend on hover
Selection, variations, render confirmation and removal work comfortably by touch; the destructive action stays visible on phones and discreet on desktop.
The header, preferences, FAQ, filters and footer now provide larger touch targets on phones and tablets while preserving ArchScene's compact visual rhythm.
The public menu is easier to use
The logo, menu button and shortcuts now provide a minimum 44 px touch target, reducing navigation mistakes when using one hand.
Language, currency and theme have more room
Selectors, FAQ rows, filters, reactions and support links are more comfortable on mobile without making larger screens feel less dense.
Sharing remains manual today, but future X automation now clearly requires a canary rollout, API credit budget and spending limit before posting.
X readiness is more honest
The modal now separates today's manual composer from the future paid API flow, avoiding any autopost promise without cost controls.
The spec records the safe path
The PRD/SDD now requires an X credit budget, spending limit, usage alert and canary account before enabling real posting.
The examples page now shows how to turn one approved render into confirmed edits, with visible cost and a fidelity guard.
The post-render path is clearer
The new block guides users to lock the best version, run one edit at a time and save the winner before testing another variation.
Cost and control appear before action
The copy reinforces 1 credit per confirmed edit, with no automatic batch spend, hidden autopost or loss of the original scene.
Signed-in billing now shows referral credits and the partner waitlist without enabling payouts, tracking or automatic commission.
The program appears where users think about credits
The billing card separates referral credits, future affiliates and optional Hotmart use while the commercial rules stay under manual validation.
Partner support opens with context
The signed-in CTA opens authenticated support with the partner subject and starter message prefilled before any payout flow exists.
The authenticated header now shows email and plan on mobile and tablet too, keeping users oriented without opening the account menu.
Identity is always visible
The signed-in area gained a compact account strip below the mobile shortcuts, with email and plan in user-facing language.
Mobile navigation stays compact
The change preserves the modern menu plus New, search and current-section shortcuts while meeting the rule that users see who is signed in.
The examples page now shows what is live, which gaps are queued and which scene an architect should bring into the next test.
The example queue is more operational
The roadmap shows live examples, next routes and the ideal input before the CTA, helping visitors choose a small proof instead of starting a batch too early.
Each route shows best input and stage
Facade, bathroom, commercial, night, clay and social now explain queue status and the safest material to validate fidelity.
The pricing page now tests interest in referral credits and affiliate partners without enabling tracking or automatic payouts.
Referrals and affiliates are separate paths
The copy separates customers who want to earn credits from partners who may earn commission on qualified paid subscriptions.
Hotmart stays a future channel, not a dependency
The block captures interest through support and a partner list while margin, terms, attribution and misuse checks stay under validation.
The social canary now separates what works today, what enters as a controlled connection and what can only become publishing with human review.
A clearer roadmap before OAuth
The Account screen shows Now, Canary and Later stages so the manual kit is not confused with autoposting.
AI media and cost stay explicit
The card keeps image upload, made_with_ai, quota, logs and spend-limit requirements visible before any API publishing.
Projects with open client details look cleaner
The projects list uses a softer fallback for work without a linked client, avoiding an error-like label on accounts with real renders.
The public project page now guides visitors to test a similar scene before scaling into batch work or portfolio publishing.
A more actionable CTA in the project showcase
The project footer now has a guided block with scene, comparison and curation steps that lead directly to a first test.
Examples remain the second decision
Visitors who are not ready to create an account can still open the examples library and compare routes first.
The profiles showcase now guides visitors to start with a render, curate approved visuals and publish the portfolio on the right plan.
Clearer CTA for new visitors
The /perfis page now lets visitors start a first portfolio render or review before/after examples before creating an account.
Commercial promise without plan confusion
The path explains that Starter helps create publishable material while the public profile remains a Studio+ feature.
The examples page now shows first-fold shortcuts for faithful render, controlled edit, social delivery and motion.
A faster mobile decision
Visitors can choose a test route before scrolling through the full library, reducing friction on smaller screens.
Context survives into the project
Each shortcut opens signup while keeping the selected route for the first project workflow.
Billing now sends accounts without a paid plan to Starter without suggesting a downgrade to users already on a higher plan.
Starter becomes the first paid upsell
When a feature requires any paid plan, the subscription path now points to the under-$10 Starter entry plan.
Upgrade notices are contextual
Accounts that already satisfy the requested plan no longer see an alert asking for a lower subscription.
The social kit now copies reviewed text, public link, render instruction, alt text and AI-media disclosure in one block.
A package ready for review
When preparing a public project, users can copy everything needed for safer manual publishing.
A safer base for future X
The flow still has no autopost, but organizes text, link, media and AI disclosure in the shape a future API integration must respect.
The examples library now explains what it costs to test a similar scene and which fidelity risk to watch in each room.
Cards are more decision-oriented
Each example now shows estimated cost and fidelity risk alongside the before/after, helping architects choose the first test.
A more honest commercial promise
The page reinforces 1 credit to validate a similar image and keeps edits, variations or video as separate confirmed steps.
The edit workbench now shows portfolio, client presentation and social post shortcuts before the free prompt while keeping review and cost visible.
Clearer commercial paths
Portfolio polish, client presentation and social crop now appear as ready workflows for turning an approved render into a deliverable.
Review stays required
Choosing a workflow opens the description mode so users can review intensity and confirm credits before generating.
The mobile and tablet dashboard replaces the long horizontal bar with a primary action, the current area and a compact shortcut menu.
Cleaner header on small screens
Instead of a row of partially hidden chips, navigation now shows New, the current area and a stable Menu button.
Shortcuts grouped by context
The menu groups Main, Tools, System and Account, making it easier to move around without dragging a mobile bar.
The logged-in comparison now makes it clear that Starter is the under-$10 low-risk entry plan before scaling to Solo, Plus or Pro.
A more visible accessible entry
The billing screen now repeats the commercial anchor for Starter, reducing doubt for users who want a small paid routine.
No billing or checkout behavior changed
This is a clarity improvement: price, credits, upgrade or downgrade actions and billing portal behavior continue to follow the existing rules.
Visitors coming from examples now see the projects list explicitly guide them through first scene and first render before expanding a batch.
A more direct first-render entry
The projects guide now frames a small pilot project, one clear image and a first render as the initial proof.
The modal stays focused on a controlled test
Project creation keeps the controlled-scene context and reinforces that comparison comes before spending credits on a batch.
The activation path now marks the first render from a completed result and keeps the SketchUp connector as an accelerator after the universal path.
First render no longer depends on the plugin
The first-render step now checks real completed renders, so users are not tied to the SketchUp milestone to prove the first scene.
Connector appears at the right moment
The path now prioritizes account, email, first render and first edit before suggesting the connector as an accelerator.
Pending steps now read as actions
Open steps show Open instead of Ready, avoiding the visual contradiction between pending status and action copy.
The examples page now shows how to turn one difficult scene into a faithful render, a controlled variation and a gallery or social-ready proof.
Next examples have a clearer workflow
The coverage roadmap is no longer just a queue. It explains the safe loop for generating more examples without scaling a batch too early.
More action before signup
Visitors understand the sequence of choosing a scene, validating fidelity, editing with control and keeping the winning version.
The Visual Edit Desk now blocks options above the available balance and asks for a fresh confirmation when users change how many versions to generate.
Confirmation follows the cost
After confirming an edit, switching from 1 to 2 or 3 options clears the confirmation so a higher spend is reviewed again.
Unaffordable options are clearer
The variation picker shows the cost for each option and explains how many credits are missing when the balance cannot cover that exploration.
Sharing guidance now prepares users for today's manual flow and a future automation path with authorization, media upload and AI disclosure.
A more faithful X checklist
The modal explains that a future integration should still keep human review, authorize the X account and upload the image before creating the post.
Clearer AI disclosure
The kit reinforces that the render should be marked as AI-generated media when the social network offers that option.
The billing screen now distinguishes future billing from an already recorded cycle, reducing confusion when subscription data is stale.
More trust in the current plan
When the cycle date has already passed, ArchScene shows the last recorded cycle instead of calling it the next billing date.
Starter stays visible in billing
The logged-in comparison still keeps Starter as the under-$10 entry option without implying a stale future charge.
The projects list no longer shows comparison before there are two public client-ready projects.
No inert button on the first visit
Users with one project and no renders see the main path to upload images, without a comparison action that cannot create a useful link yet.
Comparison appears at the right moment
The comparison link remains available once two public projects exist, matching the client portfolio workflow.
The share modal now includes a short commercial caption to turn published renders into conversations with potential clients.
Lead template in the manual composer
Alongside approval, before/after and portfolio, users can prepare a prospecting message before opening X.
More value without autoposting
The improvement stays in the safe human-review flow, without new OAuth, X tokens or automatic publishing.
The examples page now guides visitors to choose between faithful render, controlled edit, social delivery and motion before opening the workbench.
Routes inspired by the current market
The new section translates modern AI rendering product patterns into a practical decision: what to test first, what proof to watch and what next step to take.
More clarity before signup
Each route has its own CTA to start the first test without turning the public page into technical documentation.
The share modal now guides manual publishing with the same preparation a future X API integration will require.
Checklist before opening X
Users review text, download the render image and confirm the AI disclosure before publishing manually.
A safe bridge to future automation
The copy makes it clear that future autoposting needs X account authorization, media upload and AI-generated media disclosure.
As telas de precos e faturamento agora posicionam o Starter como rotina paga abaixo de US$10 para validar um projeto pequeno antes de subir para Solo.
Entrada abaixo de US$10 mais explicita
A copy do Starter reforca US$7.99/R$39, 30 creditos mensais e uso em um projeto pequeno de cliente.
Billing com decisao mais orientada
A comparacao logada explica que Starter e a entrada de baixo risco, enquanto Solo, Plus e Pro escalam com volume.
The public profiles showcase now uses an editorial placeholder while heavy render images finish loading.
Skeleton instead of an image icon
Portfolio previews no longer show an icon that could look like a broken image while renders are still loading.
More trustworthy social proof
Even when a public render takes a few seconds, the profiles page keeps an intentional look aligned with the premium visual system.
Manual sharing now makes it clearer when a render should be marked as AI-generated media before publishing.
Reminder before manual publishing
When the render is ready to attach, the modal reminds users to mark it as AI-generated media if the social network asks for that confirmation.
Transparency without autoposting
The flow still uses a manual composer, public link, downloadable image and human review, with no new OAuth or automatic publishing.
The public profiles page now keeps a clearer visual preview while portfolio renders load.
Less empty above-the-fold preview
The active portfolios panel now has an editorial placeholder and higher loading priority for the first visible renders.
A steadier first impression
Even when the image proxy takes a few seconds, the public showcase no longer looks like an empty dark block.
The signed-in dashboard now gives more width to project, image, render and credit metric cards on desktop screens.
No awkward word breaks
Metric cards are no longer squeezed into four columns inside the main dashboard area, preventing labels from breaking mid-word.
A more professional first read
The progress area stays compact, but numbers and descriptions are easier to scan on the first visit.
The project guide now shows why guided generation still needs an image before the CTA becomes available.
Visible reason on the blocked CTA
Before the first upload, the Generate first render button stays unavailable and explains that a renderable image is required.
More accessible state
The explanation is associated with the blocked button, helping screen readers and reducing uncertainty during the first test.
The pricing page now shortens the path between the free test and the low-risk entry plan.
A faster mobile decision
The Starter block now has a direct call to view the entry plan before the full pricing cards.
Less pressure to jump into bigger plans
The copy reinforces that visitors can start small, cancel anytime and upgrade only when volume requires it.
The social kit now opens the X composer with reviewable text, a separate public link and short ArchScene hashtags.
A cleaner composer
The project link no longer gets mixed into the X text body, reducing duplication and making the public card more predictable.
Social discovery is more ready
Manual posts now include ArchScene and RenderArquitetonico hashtags without autoposting, new tokens or publishing before human review.
The first signed-in dashboard now gives more room to the create, gallery, examples and audit shortcuts.
Quick actions without clipped text
Shortcut cards no longer squeeze four actions into the same row on medium screens and keep the supporting copy visible.
A calmer first decision
The home screen still prioritizes the next step, now with steadier cards for choosing project, gallery, example or audit.
The examples library now shows which difficult room types are queued for the next validation rounds.
More variety without fake imagery
The page lists facades, bathrooms, small commercial spaces, night lighting, raw models and social candidates as test routes.
Clear criteria for every new example
Each route explains what to upload and what signal to judge before turning a room into a batch or post.
The pricing page now shows the Starter entry price at the top, next to the free test.
Entry price is easier to see
Visitors see Starter from $7.99 or R$39 per month before reaching the full plan cards.
Free test and first paid plan are connected
The hero reinforces 5 free credits with no card and shows the low-risk paid next step.
Render sharing now prepares the image, caption, link and a copyable accessibility description.
Image description ready for the render
When the social kit offers the render image, it also shows a short alt text users can copy into the social network.
Safer modal on short screens
The social kit modal now scrolls internally, keeping caption, image and accessibility fields reachable.
Visitors coming from the examples page now reach the logged-in area with a clear playbook for validating the first scene.
Signup preserves the chosen route
Example buttons now open the project workbench with the selected test context instead of losing the intent at login.
Guided first test in the logged-in area
The projects page shows a short three-step block to create a small project, compare fidelity and only then expand the batch.
The before-and-after library now guides which scene to test first based on the risk the architect wants to validate.
Decision matrix before the playbooks
Visitors can choose between fast confidence, geometry check or portfolio-ready image before creating an account.
Less doubt before signup
Each path explains what it is for, what to validate and which image type to use as the first test.
The support screen now respects phone width more reliably and avoids horizontal scrolling while opening a conversation.
Cards contained in the mobile grid
The contact and new-conversation blocks now shrink correctly inside the screen instead of pushing the layout sideways.
More predictable attachment field on phones
The file field stays contained inside the form, keeping the support area more stable on narrow screens.
The public before-and-after library now turns playbooks and example cards into clearer paths for testing one of your own scenes.
Playbooks with a next click
After choosing a first-scene route, visitors now see a clear call to start the test without going back to the top of the page.
Example cards with contextual action
Each visual example now offers a similar-scene test, keeping fidelity proof connected to signup.
Render sharing now keeps the text, public link and downloadable image in the same flow before opening X.
Post image next to the draft
When the social kit starts from a recent render, the modal offers the image download so the user can attach it manually in the X composer.
Safer publishing without a new token
The flow stays on Web Intent and human review: prepared text, public link and downloadable image, with no autopost or OAuth before the canary.
The project workbench now sends new accounts to the guided path before opening the technical generation panel.
Smarter Render shortcut
Before the first result, the Render card opens the first-render guide; after that, it returns to the full generation panel.
More direct next step
The page now recommends generating from one ready image and comparing before/after instead of suggesting parallel paths too early.
The Gallery now helps new accounts move out of the empty state and continue directly in the active project.
Clearer next step
When the library has no items yet, the primary CTA can open the latest project to upload the first source image.
Less friction before the first render
The empty state explains that the image starts inside the project and returns to the Gallery once the render is ready for editing.
The authenticated pass fixed small billing UI friction and made the Portuguese credits statement more consistent.
Plan-change button no longer clips
Long labels such as downgrade to Starter now wrap inside the button instead of overflowing the card.
Credits statement copy reviewed
The credits page received clearer Portuguese wording for balance, entries, debits and refunds.
The pricing page now helps visitors choose between the free test, the accessible Starter plan and an upgrade for higher volume.
Starter is easier to understand
The $7.99 or R$39 plan is framed as the first paid routine after one good render, before jumping into Solo.
Less doubt before the cards
A quick choice guide explains when to stay on 5 credits, when to enter Starter and when to move up to Solo or Plus.
The library now includes practical playbooks for choosing a real scene, judging fidelity and deciding when to scale into a batch.
First-test playbooks
Visitors can choose between joinery, exterior areas, SketchUp scenes or client-ready comparisons before opening the workbench.
Clearer approval criteria
Each playbook explains what to upload, what to check and what to do next without exposing internal technical terms.
The describe-change mode now organizes common requests into reviewable recipes for light, materials, delivery and cleanup.
More guided edit recipes
Architects can choose a ready intent, review the text and apply the recommended strength before spending a credit.
Preservation remains the rule
Each recipe starts with fidelity language to preserve layout, materials, furniture and the project reading.
The post preview is now an editable draft with a counter before opening the manual X composer.
Editable social draft
Architects can adjust the message, keep the public link and copy the final text without leaving the modal.
X uses the reviewed text
The post on X button now opens the composer with the edited draft, preserving human review and avoiding autopost.
Project sharing now prepares a short, copyable and reviewable preview before opening the manual X composer.
Safer manual composer
The share modal now explains that X opens for human review, with no autopost and no new token in the browser.
More controlled social text
The caption sent to the composer is kept compact so the public link is preserved and the post does not become too long.
The before/after library now shows how to turn visual proof into a controlled test with the architect's own project.
Bridge from example to action
The examples page now has a three-step guide to choose a clear scene, compare fidelity, and only then scale the batch.
CTA closer to the visual proof
After understanding what to inspect in examples, visitors find a direct prompt to test their own scene or review plans.
The pricing page now explains when to move from 5 free credits to the first low-risk paid plan.
First paid step is easier to understand
A new band summarizes the path: validate without a card, enter Starter with 30 monthly credits, then grow into Solo, Plus or Pro when volume increases.
More clarity before the plan cards
Starter's value appears before the full plan comparison, helping architects understand R$39/mo or $7.99/mo without changing checkout behavior.
The recent renders shelf now gives architects a direct path to prepare reviewed sharing without posting anything automatically.
Social kit on the featured render
While reviewing a recent render, users now find the sharing shortcut on the image card itself, next to open, download and choose for delivery.
Privacy before posting
If the project is still private, ArchScene points users to public profile setup before opening any social composer.
The entry plan now has the subscription contract it needs and a clearer message while checkout activation is still pending.
Entry plan aligned with billing
Starter is now covered by the subscription contract and the price variables needed to activate checkout in USD or BRL.
No technical error for clients
If a price is not active in the current environment, ArchScene shows a human explanation instead of exposing internal Stripe details.
The examples page now organizes before/after pairs by space type and shows what to inspect in each visual proof.
Filters by project type
Visitors can switch between all examples, living/suites, kitchens, balconies and outdoor areas using the same real project and render pairs.
More objective visual proof
Each card explains which fidelity cue to inspect, helping architects decide whether to test ArchScene with their own image.
A pagina de precos e o faturamento agora incluem o Starter, um plano de entrada com 30 creditos mensais antes do upgrade para Solo.
Entrada paga menor para validar projetos reais
O Starter aparece em /precos e no billing com preco em USD/BRL, creditos mensais, custo por credito e caminho claro para evoluir quando o volume de renders crescer.
The sign-in screen now adapts its title, helper copy and button when you arrive from the gallery, credits or support.
Context preserved before access
Architects who try to open the gallery now see a clear prompt to sign in and return directly to the visual workbench instead of a generic projects message.
The sign-in screen now waits for the browser to prepare the secure login before enabling submission, avoiding an error page while the tab is still loading.
No native submit before the session is ready
Email, password, remember-me and submit controls stay briefly disabled during initial hydration, so the browser no longer falls back to a native POST to /login.
The gallery now makes it quicker to open, browse and download larger images, especially on mobile.
Open preview from the whole card
Clicking the card image opens the enlarged viewer, with a visible mobile button, position counter and previous/next navigation.
Larger review without losing context
The modal supports Esc, keyboard arrows and backdrop close; the side panel scrolls on small screens and can download source images too.
The public support page now explains when to use email/general contact and when to sign in to open a project, render, credit, or attachment case inside the studio.
Clear boundary between channels
Public support is for general help, access, billing, and security; project cases are directed to the authenticated chat.
Signed-in users go to the right channel
When an account is already active in the browser, the page sends users to authenticated support so history, files, and credits stay in context.
Entering ArchScene is clearer on small screens: the main signup CTA appears earlier, Google has an environment-aware fallback, and the hero text stays readable for accessibility.
Mobile signup keeps the CTA above the fold
The signup page compresses repeated reassurance copy on phones so the primary button stays reachable without a long scroll.
Social login has a clear fallback
When Google is not enabled in an environment, ArchScene explains the email fallback instead of silently hiding the social path.
The public showcase is clearer: render cards on the profile, embed and PDF now use the project name as the main context instead of repeating only “Render”.
More descriptive render cards
Selected renders now show the associated project as the title while keeping the render label as supporting visual context.
Better accessibility and sharing
Alt text, links, embed and print views include project context so public portfolios feel more professional for clients.
After saving an account photo, the dashboard header and sidebar use the same visual identity as the public profile.
Consistent avatar in the header and sidebar
The account menu, sidebar account card and dashboard shortcuts now show the saved photo, with initials only as the fallback.
More useful account card
The sidebar now includes name, email, plan and shortcuts to account settings and the public profile.
The instant profile photo preview now preserves the file in the form, so Save publishes exactly the image the user selected.
Preview without clearing the input
When a valid photo is selected, ArchScene updates the local preview without clearing the file that will be uploaded on save.
Account editing is safer: selecting a photo updates the preview immediately, the save button shows progress and avatar upload failures return a clear message instead of breaking the page.
Local preview before saving
Users see the selected photo immediately before publishing the profile change.
More resilient avatar upload
The profile action validates the file safely, catches read/upload failures and redirects back to account settings with a clear message.
Profile editing is cleaner: photos are now managed through preview, upload and removal while the technical Storage URL stays hidden on the backend.
Technical storage link removed from the profile form
The account page no longer shows raw storage URLs and the server preserves the current photo when no new image is uploaded.
Clearer photo replacement and removal
Users can see the current photo, upload a new image or mark the photo for removal without handling Storage details.
Public showcases are cleaner in the HTML and browser payload too: profile projects use the public title or a safe fallback instead of raw workbench names.
Safe names in the public profile payload
Project cards on the public profile and print/PDF view no longer serialize internal names when a public presentation title exists.
Public showcases are more client-ready: featured renders now use the project's public title when available, avoiding provisional or internal workbench names across the profile, embed and PDF.
Renders prefer public project titles
Public profiles, embeds and print/PDF views now prefer the published project title before falling back to the internal workbench name.
More professional profile sharing
Profile pages are safer to send to clients, partners and social networks without leaking test names.
The architecture visual network now works better for architects, designers, studios and the ArchScene team: public profile links open without login and account roles include Founder/CEO and Developer/founder.
Public profile links without login
URLs such as /jean now open for visitors without a session while reserved routes such as dashboard and admin stay protected.
Founder and developer roles on profiles
Account profiles now include Founder/CEO and Developer/founder roles so product creators do not have to present themselves as architects.
Visual network copy aligned with the niche
The profiles page now positions architects, designers, studios and the ArchScene team as part of the product's architecture visual community.
Beta operations are safer on mobile: admins see incidents, new users, support and the AI queue before long tables, with compact lists that stay inside the screen width.
Mobile summary for faster response
The first admin fold on phones now highlights incidents, new signups, support and the AI queue with direct shortcuts to act.
Wide tables are controlled on mobile
Jobs, failures and user search now use compact cards on phones while keeping the full tables for larger screens.
Admin forms resist overflow
Credit controls, assisted user creation and operational notices now respect the available width on narrow screens.
The first-run experience is more guided: new users see a safe client-presentation example, understand the next project step, and admins can spot where each account stalled in the funnel.
Presentation example without spending credits
Dashboard and project pages now point to a static public example showing 2D, before/after review and client handoff without calling AI or using project data.
Next onboarding step is clearer
The checklist now reinforces where the user is and what action comes next, especially between creating a project and uploading the first image.
Admin follow-up for new users
The user detail highlights whether someone stopped before project, upload or render, and the admin queue replaces technical quality values with product language.
Project presentation is safer to hand off: 2D/3D links explain public state clearly, the tour avoids technical filenames, and public pages protect temporary names.
Presentation links are clearer
The links card separates 2D page, 3D tour and public/private state without showing the uploaded 3D filename.
Public pages hide temporary names
Public 2D and 3D project pages reuse beta-safe titles so internal or test names do not leak into shareable URLs.
3D tour speaks like a client handoff
Public tour copy replaces GLB, manifest and technical-preview language with guided review and a simple fallback to the 2D presentation.
Gallery, queue and project pages are more demo-ready: internal names are replaced with client-facing labels, render copy avoids model jargon, and cards load lightweight previews.
Internal names stay out of demos
Projects, scenes, uploads and renders with temporary-style names now appear with presentation-ready titles instead of temporary filenames or backstage language.
Render review without technical jargon
Result cards now describe a project-faithful profile and user-friendly quality, instead of showing model IDs or raw technical values.
Lighter gallery browsing
Cards and queues use optimized thumbnails while the full file remains available for large preview, comparison, download and editing.
Collapsed gallery groups now show context and a direct action to compare, edit or open the scene, making the gallery feel less passive.
Primary action on collapsed groups
Scenes with a finished render now expose a Compare / edit shortcut without requiring the user to open the group first.
Counters explain what is inside
Each group now shows how many sources, renders and edits exist in that scene, so users know what they are about to review.
Search and sorting are more accessible
The search input and sorting selector received explicit accessible names for better assistive navigation and QA snapshots.
We polished dashboard labels and copy: Account now reads cleaner, Agents is less technical, and project cards show counters with context.
More trustworthy profile and showcase copy
The Account screen clarifies that the ready signals belong to the public showcase, so they are not confused with the full profile-completion percentage.
Less raw agent configuration language
The Agents screen now uses friendlier labels and formats the credit balance consistently with the rest of the product.
Project-card numbers have labels
Project cards now show counters as images and renders instead of leaving bare numbers beside icons.
The render history now has quick filters and a dedicated delivery-selection area that makes the chosen best result explicit.
Quick filters in render history
Users can switch between all, recent, selected, failed and in-progress renders without losing project-page context.
Best result is more obvious
The project page now shows a delivery-selection card and highlights the chosen render in history, reducing uncertainty about which image to send to the client.
Clearer review actions
The selection button now communicates that the user is choosing the render for delivery, not just marking a generic item.
Project pages now include a recent-render shelf near the top, with preview, date, source and shortcuts to open, download or mark the best result.
Latest generated images shelf
Newest renders now appear before the queue and heavier controls, so users do not have to hunt through the full history at the bottom of the page.
Direct review shortcuts
Each recent render shows source, status, quality and quick actions to open the result, download the image or mark it as the best delivery.
Clearer full history
The results section is now labeled as the complete history and states that newest renders come first, reducing review confusion.
The first-render flow is more visual: the screen shows source image, model, cost, balance and expected result before sending work to AI.
Guided primary generation action
The render area now combines chosen source, default model, estimated cost, balance and confirmation in one easier-to-understand card.
Source images as a visual workbench
The ready-to-render image list became a card grid with larger previews, quality, status, size, cost and a direct generation CTA.
More honest generation copy
Instructions reinforce that AI improves visual presentation without redesigning the project, with clearer cost and confirmation before credits are used.
The admin cockpit is more stable for review, with emails masked by default, clearer credit metrics and tighter mobile navigation.
Lower visual-error risk in Admin and Gallery
Critical dashboard dates now use a stable timezone, reducing server/browser differences during hydration.
Better privacy for admin screenshots
Admin lists and cards now mask emails by default, keeping sensitive data less exposed during reviews and screen sharing.
Credits read more clearly
The admin now separates consumed, granted/renewed and refunded credits more clearly when tracking AI cost.
More contained mobile dashboard navigation
The mobile bar and admin tables gained horizontal containment to avoid accidental sideways scroll in the cockpit.
The edit desk now separates project-faithful adjustments from creative variations, making it clear when an edit can change how the proposal reads.
Fidelity-first presets
Lighting, texture, cleanup and materiality edits stay in the preservation group, reinforcing camera, layout, millwork, major materials and proportions.
Marked area edits
You can now click the render area that needs attention and describe the change, with localized instructions to preserve the rest of the image.
Main image as the source of truth
The base render is now more prominent in the edit desk and the prompt reinforces that the AI must treat the approved image as the primary reference, not loose inspiration.
Gallery scenes open with less waiting
The gallery now prewarms covers and the first likely images for each scene, so render groups feel more immediate without downloading the full library at once.
More options in one request
The edit desk can generate 1, 2 or 3 versions for comparison while showing cost, balance and remaining credits before confirmation.
Creative variations with warning
Adding people or humanizing a scene is separated from the default flow and warns that it may change the reading of the project.
LED without automatic invention
Lighting refinement no longer suggests adding LED strips where they feel visually useful. It now enhances only visible or explicitly specified lights.
LED sem invenção automática
O refinamento de iluminação deixa de sugerir fita de LED onde fizer sentido e passa a realçar apenas luzes visíveis ou explicitamente indicadas.
We added English public pages for high-intent US search queries while keeping Portuguese pages active for Brazil.
New English discovery pages
New routes target AI architecture rendering, SketchUp AI rendering, batch rendering for architects and before/after architecture rendering.
en_US metadata
English pages now use OpenGraph, keywords and search copy aligned with the American architecture market.
Sitemap and robots updated
The new routes are automatically included in the sitemap, robots rules and the public AI assistant guide.
We added public pages around real architect search intent and made sitemap, robots and structured data clearer for search engines and assistants.
Search-intent pages
New pages explain AI SketchUp rendering, batch rendering, before/after proof and AI rendering for architecture with organic search language.
Clearer sitemap and robots
Google, Bing and assistant crawlers receive clear public paths while dashboard, APIs and auth stay out of indexing.
Structured data for discovery
The site now describes ArchScene as design software with organization and FAQ data, helping search engines understand the product category.
Guide for AI assistants
We added a public product summary and key links so assistants and discovery engines can understand ArchScene faster.
The edit desk is now more conservative, improving light, texture and presentation without redesigning the approved space.
Locked fidelity for edits
Render edits now prioritize camera, layout, furniture, millwork, major materials and proportions before applying any visual adjustment.
Safer quick presets
One-click edits no longer suggest free floor, plant or furniture changes and now enhance existing project elements instead.
A fila de renders agora tenta abrir a imagem pelo endpoint seguro da galeria quando a prévia direta ainda não veio pronta.
Fallback autenticado para miniaturas
Resultados concluídos podem mostrar o render ou a cena original mesmo quando a URL assinada direta não foi gerada na primeira leitura.
Menos ícones genéricos no dashboard
O painel fica mais visual para o arquiteto acompanhar os últimos resultados sem precisar abrir cada projeto.
A fila do dashboard voltou a mostrar miniaturas dos resultados recentes quando já existe imagem disponível.
Miniaturas na fila de render
Resultados concluídos agora usam os buckets corretos para exibir a prévia no painel, em vez de cair no ícone genérico.
Reconhecimento visual mais rápido
O arquiteto consegue identificar o render recente pela imagem antes de abrir o projeto completo.
Avisos automáticos antigos ficaram mais equilibrados para o admin entender o histórico sem confundir com pane ativa.
Banner operacional mais claro
Notificações de instabilidade registradas agora orientam a conferir o estado atual antes de comunicar usuários ou iniciar deploy.
Menos ruído no cockpit
O alerta deixa de usar linguagem de emergência quando o incidente já está normalizado no status do ArchScene.
Os avisos de operação ficaram mais úteis para acompanhar o beta sem expor detalhes técnicos desnecessários.
Avisos críticos menos agressivos
Alertas automáticos agora aparecem com linguagem de operação e levam o admin para o incidente certo, sem dominar a experiência do usuário.
Status público mais limpo
A página de status prioriza impacto, acompanhamento e tempo de operação, deixando o diagnóstico técnico para o cockpit admin.
Deploy blue/green entendido pelo monitor
O monitor reconhece melhor o slot ativo antes de avisar instabilidade, reduzindo falsos alarmes durante atualização segura.
The team can receive Telegram signals for key beta events such as new users, confirmed payments and support requests.
New users in near real time
Real signups can alert the operation team so the first project is monitored before the user drops off.
Confirmed payments on Telegram
Stripe payment and renewal events now have an operational alert after the webhook confirms and records the event.
Faster support during promotion
When a user opens a support thread, the team can receive a direct link and respond while the test is still warm.
Password recovery and account confirmation now have dedicated templates instead of relying on Supabase's default message.
Branded password recovery
The reset email now shows the ArchScene lockup, Portuguese copy and a short English fallback for international users.
More professional account confirmation
The first access email explains the next studio step and reinforces that projects are private by default.
Old sender isolated
The operations runbook separates app emails from native Supabase Auth emails so inherited sender names and subjects do not return.
Cadastro e recuperação de senha passam por um callback mais testável, com retorno seguro ao estúdio e orientação de suporte quando o email não chega.
Boas-vindas em PT e EN
O primeiro email depois do cadastro usa o idioma ativo do usuário e explica créditos, privacidade, suporte e o caminho para gerar o primeiro render.
Troca de senha dentro da conta
A área de conta ganhou um card de segurança para atualizar senha sem depender do fluxo de recuperação por email.
Confirmação mantém o destino certo
Quando o usuário começa o cadastro a partir de uma área específica, o link de confirmação preserva esse destino seguro depois do login.
Recuperação com fallback claro
A tela de recuperação agora orienta o usuário a falar com suporte caso o email não chegue em alguns minutos.
Checklist de QA para inbox real
O fluxo de cadastro, confirmação e nova senha ganhou um roteiro seguro para validar caixa de email sem registrar links privados.
Signup and password recovery now use a more testable callback, preserve safe studio redirects and explain the support path when an email does not arrive.
Confirmation keeps the right destination
When users start signup from a specific area, the confirmation link preserves that safe destination after login.
Recovery has a clearer fallback
The recovery screen now points users to support if the email does not arrive after a few minutes.
Inbox QA checklist
Signup, confirmation and password reset now have a safe validation checklist that avoids recording private email links.
Projects now show what is public, when the 3D tour is ready and which links can be sent to clients.
Presentation links on each project
The project screen now has a safer panel for copying and opening the public 2D presentation.
3D tour only when ready
The 3D shortcut only appears when there is an active ready model, avoiding incomplete client links.
More honest sharing
The public page remains useful in 2D even without a 3D model, with clear copy about what is available.
A entrada social ficou protegida contra retornos para endereços internos do servidor durante troca blue/green.
Retorno seguro ao estúdio
Depois de autenticar com Google, o usuário volta para archscene.com em vez de herdar portas internas usadas no deploy.
Callback mais estável
O fluxo de autenticação agora normaliza a origem pública antes de redirecionar para projetos, recuperação de senha ou login.
Google sign-in is clearer when an attempt expires or is retried after signing out.
Expired session without a technical screen
When the Google link expires, the login screen shows a simple retry instruction instead of a raw technical error.
Friendlier access errors
Social authentication failures now become short, actionable messages for users entering the studio.
O ArchScene agora pode oferecer login e criação de conta com Google, mantendo email e senha como alternativa.
Botão Google no acesso
Quando o provedor estiver habilitado no ambiente, usuários podem entrar ou criar conta usando Google.
Configuração segura por ambiente
O app só exibe provedores liberados por configuração, enquanto o segredo OAuth fica restrito ao Supabase Auth.
O fluxo de login ganhou mensagens mais humanas para criar conta, recuperar senha e voltar ao estúdio com segurança.
Email de recuperação sem confusão
A tela de recuperação explica que o link só é enviado quando a conta existe, sem expor dados de cadastro.
Nova senha com padrão mais forte
A redefinição agora orienta senhas com pelo menos 8 caracteres e mensagens de erro mais claras.
Mensagens de autenticação revisadas
Textos internos e sem acento foram trocados por mensagens prontas para usuários beta.
ArchScene now has a guardrail for reviewing PRs in preview environments without accidentally triggering real billing.
Live Stripe blocked in preview
If a temporary preview is misconfigured with a live key, checkout, the billing portal and subscription changes are blocked.
Safer visual review
The recommended flow now clearly separates visual preview, local testing and VPS production.
Preview checklist documented
The team has a short checklist for validating landing, login, status, health and billing without mixing environments.
Logged-in navigation, gallery actions and quick controls now have larger touch areas, clearer focus states and more readable small labels.
Larger button targets
Primary actions and icon buttons now respect more comfortable minimum target sizes for mouse, trackpad and mobile.
Gallery is easier to operate
Selecting, enlarging, opening menus and using batch actions is less cramped on dense cards.
Clearer focus and labels
Operational links and helper labels gained visible focus, better contrast and less exaggerated spacing.
The final i18n pass standardized visible dashboard balances, level progress and render edit cost copy.
Standardized dashboard balance
The navigation balance now uses the same localized number format used in billing and project screens.
Localized level progress numbers
Render counters in the gamification card and public proof stats now follow the active language.
Clearer render editing cost
The edit drawer shows current balance and remaining balance with the right EN/PT number format.
Conta, créditos, auditor, onboarding, playlists e conector SketchUp ficaram mais consistentes com EN/PT e datas menos ambíguas.
Extrato de créditos mais legível
Saldos, totais e movimentações agora seguem o formato do idioma ativo, incluindo data e hora no histórico.
Fluxos operacionais padronizados
Auditor, onboarding e playlists usam contagens localizadas em mensagens de custo, progresso e confirmação.
Conector SketchUp com datas claras
Chaves do plugin mostram criação e último uso com data e hora no formato correto para EN/PT.
Painel, projetos e admin ficaram mais coerentes com o idioma ativo, usando números localizados e datas com ano completo.
Números seguem o idioma ativo
Métricas do dashboard e da lista de projetos agora respeitam o formato de milhares do idioma escolhido.
Datas menos ambíguas
Projetos e usuários no admin passam a mostrar datas com ano completo, reduzindo dúvida em revisões de beta.
Plugin traduzido no painel
Os passos de instalação do plugin SketchUp agora acompanham EN/PT em vez de ficarem fixos em português.
A página inicial no celular ficou mais curta, com prova visual mais cedo e um CTA sempre fácil de encontrar.
CTA fixo no mobile
Quem visita pelo celular agora consegue começar grátis ou voltar aos exemplos sem procurar o botão no meio da página.
Prova visual reforçada acima da dobra
O hero ganhou uma dica clara para comparar cena do SketchUp e render final no before/after.
Menos repetição antes dos planos
Blocos secundários ficam mais discretos no mobile e uma faixa resume prazo, revisão, arquivos aceitos e créditos protegidos.
A página de preços ficou mais direta para novos usuários entenderem o teste grátis, o custo por crédito e quando vale escolher Solo, Plus ou Pro.
CTA de teste no topo
O hero de preços agora oferece começar com 5 créditos grátis antes de pedir decisão de plano.
Regras de crédito antes dos cards
A página explica que 1 render padrão usa 1 crédito, preparação SKP não consome IA e falhas técnicas devolvem crédito.
Planos com menor fricção
Os botões dos planos ficaram menos agressivos e os cards mostram o custo aproximado por crédito.
A tela de cobrança separa saldo, créditos mensais e créditos extras para deixar a assinatura mais fácil de confiar antes de pagar ou trocar de plano.
Saldo de créditos explicado
O plano atual agora mostra o saldo disponível, os créditos que renovam todo mês e os créditos extras em blocos separados.
Cobrança anual mais evidente
Os botões anuais indicam a economia aproximada em meses, reduzindo dúvida entre mensal e anual.
Portal de cobrança com contexto
A página explica que o portal serve para trocar plano, atualizar cartão, cancelar e baixar faturas.
Pequenos textos de contagem no admin, galeria e monitoramento ficaram mais humanos e sem pluralização de protótipo.
Contagens sem atalhos técnicos
Mensagens como usuários, alvos, eventos, lotes e falhas agora aparecem com plural correto em vez de formatos com parênteses.
Monitoramento mais legível
Alertas de fila IA e saúde do sistema usam números formatados para leitura rápida durante operação do beta.
A lista de projetos ficou mais fácil de escanear, com títulos menos cortados, status menos invasivo e grade mais equilibrada em telas largas.
Títulos com mais respiro
Os nomes dos projetos podem ocupar até duas linhas antes de cortar, ajudando a reconhecer obras com nomes longos.
Status separado do nome
O selo de status saiu da mesma linha do título para não competir com o nome do projeto.
Grade mais completa
Em telas largas, a lista usa quatro colunas quando couber e reduz o efeito de card isolado na segunda linha.
CTA acompanha o estado do projeto
O botão principal agora indica se o próximo passo é enviar imagens, gerar render ou revisar resultados prontos.
A navegação lateral do dashboard ficou mais enxuta e separada por contexto, ajudando o arquiteto a encontrar projeto, ferramentas e suporte sem ruído.
Navegação agrupada por uso
Painel, projetos, galeria e playlists ficam no grupo principal; auditor, agentes, faturamento, suporte, status e admin aparecem em áreas próprias.
Estado ativo mais claro
O item aberto na lateral ganhou contraste e marcador mais forte, incluindo faturamento e status.
Compra de créditos mais explícita
O botão de compra agora deixa claro que leva ao saldo de créditos, reduzindo ambiguidade no topo do app.
A tela de entrada ganhou uma área visual mais centralizada, deixando logo, chamada e comparativo mais harmônicos no primeiro contato.
Marca centralizada no painel visual
Logo, selo e chamada principal agora ficam alinhados ao centro do container esquerdo no desktop.
Comparativo com largura controlada
A pré-visualização antes/depois mantém proporção e respiro dentro do painel, sem competir com o formulário de entrada.
Mensagem de saída corrigida
A confirmação ao sair da conta volta a exibir acentuação correta na tela de login.
Login sem rolagem no desktop
O painel de entrada foi compactado para caber melhor na primeira tela em notebooks e monitores menores.
Exemplos expandem sem sair da landing
O CTA de transformações agora abre os oito comparativos na própria página inicial, mantendo o visitante no fluxo.
Imagem maior da galeria volta a abrir
A comparação em tela grande agora carrega as imagens internas da galeria sem cair no erro de visualização.
The authenticated home screen is more operational on mobile: the render queue moves up and progress/history are collapsed.
Queue before gamification
The dashboard now prioritizes next action, essential metrics and render queue before progress blocks.
Collapsed progress on mobile
Goals, achievements, leaderboard, streak and heatmap live inside an expandable block to reduce initial scrolling.
The dashboard now has a more operational render queue, separating current work from recent results and showing previews when an image is available.
Current queue and recent history
Active renders and failures are separated from the latest completed results, reducing repetition on the main dashboard.
Cards with visual previews
When a result or source image is available, the queue shows a thumbnail so users can recognize work faster.
Fewer technical IDs on screen
Job and result IDs moved out of the main card body and remain only as technical item details.
The render queue now uses the shared i18n formatting foundation for dates and numbers, reducing ambiguity in dashboards and projects.
Fuller queue dates
Recent jobs no longer rely on short dates like 05/07 and instead show less ambiguous localized dates.
Standardized numbers
Metrics, refunded credits, queue position and image counts now follow the active language formatting.
First i18n cleanup round: Billing and internal operational surfaces now format dates, numbers and credits more predictably in Portuguese and English.
Less ambiguous dates in English
When the interface is in English, Billing now shows dates like May 17, 2026 instead of ambiguous numeric dates.
Credit copy with clean Portuguese accents
Wallet messages and visible internal labels no longer show broken Portuguese accent encoding.
Shared formatting foundation
Number, date and credit helpers reduce the chance of future screens falling back to raw formats.
Plugin 0.9.6 gained a direct upload path to private storage, reducing load on the main server during batch exports.
Direct scene upload
Instead of sending every large image through the main endpoint, ArchScene now issues a signed URL and the plugin uploads the scene directly to Storage, then registers it in the project.
Old plugin compatibility
The previous multipart endpoint remains available as a fallback for users who have not updated the exporter yet.
More reliable progress
The flow preserves temporary code, scene, materials, file size, dimensions and project context so the dashboard stays in sync without routing the full file through the app server.
O ArchScene ganhou uma camada de vigilância recorrente para acompanhar site, banco, arquivos, fila de IA e recursos do servidor antes que uma instabilidade vire surpresa para os testers.
Health check recorrente
Um cron protegido registra snapshots de produção e usa os sinais do /status para acompanhar o funcionamento do produto.
Incidentes automáticos
Quando a fila de IA trava, o banco falha ou o servidor entra em atenção, o sistema cria ou atualiza um incidente operacional para o admin agir rápido.
Alertas para administradores
Admins recebem aviso interno quando o monitor detecta degradação, com cooldown para evitar ruído durante o beta.
Admins now have a safer flow for sending messages to users and beta segments, with a preview before sending and less technical wording.
Preview before sending
The notifications screen shows audience, type, severity, delivery channels and message appearance before dispatch.
Beta-operations wording
Visible copy now uses clearer message language instead of internal broadcast terminology while keeping history and auditability.
Clearer user search
Sending to a specific user now has clearer labels and empty states for support follow-up.
The beta now has an operational alert for earlier follow-up: when a real account receives its initial wallet, admins get an in-app notification with a direct link to that user detail.
New-user alert for admins
Real signups now create an internal admin notification without blocking signup if the alert cannot be delivered.
Direct onboarding follow-up link
The notification opens the admin user detail, where the team can review profile, credits, projects, history and next steps.
Less noise from test accounts
Test emails and admin accounts are ignored by the automatic alert so the cockpit stays focused on real users.
We polished messages that still felt like prototype text in Portuguese and English. Render actions, gallery, playlists, SketchUp plugin feedback and balance warnings now use human language with clearer plural wording and less technical noise.
Credit copy feels like product language
Cost, insufficient-balance, render-confirmation and refund messages no longer show prototype placeholders. They now read as natural product copy.
Scene and image counts are clearer
Gallery, playlists, SKP import and plugin uploads now describe scenes, images and renders with cleaner count labels for architects.
SketchUp flow messages are easier to trust
Partial reception, scene limits and SKP import notices now explain the real state without odd abbreviations or technical copy.
The gallery is now more direct for daily work: sources and renders are split into tabs, renders from the same scene are grouped, scenes can be renamed, renders can be edited with one click, and credit cost is clearer. This release also improves theme contrast, accessibility and batched image loading.
Gallery tabs and render groups by scene
The 'Scenes & sources' tab is separated from 'Renders & edits'. Multiple results from the same scene now appear in a collapsible group with a cover image and count, so users can scan scenes quickly and open only what matters.
Edit a render without writing a prompt
The editing bench opens in quick-edit mode with 8 one-click adjustments, including warmer light, golden hour, cleanup, more greenery, minimal styling and realistic textures. The detailed 'Describe change' mode remains available.
Less scrolling and clearer controls
The gallery header is leaner, repeated filters were combined, view controls are integrated with search, and batch actions stay close while items are selected.
Gallery images load in batches
The gallery mounts fewer images on first load and lets users load more items on demand, making the first navigation lighter for accounts with many scenes and renders.
Clear credit math
Every credit-spending flow now shows the same simple calculation: cost, current balance and balance after the action.
Theme contrast, switcher and notifications
Fixed text that could disappear in dark and sepia themes. Theme switching is instant, and the notification badge clears correctly when opened.
Accessibility polish
Keyboard focus is visible across gallery controls, reduced-motion preferences are respected, and the theme switcher uses localized labels.
Esta release traz três coisas que arquiteto pediu: 1) compartilhar projeto com 1 clique pra cliente, 2) apresentar renders em modo fullscreen, 3) refinar qualquer render com novos lighting presets.
Compartilhar projeto
Botão Compartilhar no header do projeto abre modal com link público copiável + envio rápido pra WhatsApp, LinkedIn, X, e-mail e legenda pronta pro Instagram.
Modo apresentação (slideshow)
Botão Apresentar abre os renders do projeto em fullscreen com setas pra navegar, auto-advance opcional, thumbnails de pulo rápido e atalhos de teclado.
Refinar render existente
Cada render tem botão Refinar que abre um modal com 5 ajustes de luz (LED, luz quente, spots/sancas, mais luz natural, cena noturna) — re-renderiza preservando layout, materiais e composição. Custa 1 crédito.
Renomear projeto inline
Click no título do projeto vira input editável com Enter pra salvar e Esc pra cancelar. Optimistic UI mostra o novo nome imediato.
OG image dinâmica nas páginas públicas
Compartilhar link de projeto público no WhatsApp/LinkedIn agora gera uma OG card 1200×630 com cover image, título, nome do arquiteto e brand ArchScene.
Páginas de senha com brand
/login/forgot-password e /login/reset-password agora têm logo ArchScene clicável + trust strip explicando o fluxo, em vez de um card isolado sem contexto.