Why Builders and Members See Different App Versions

When builders and members see different versions, it is by design. A builder editing an app works on a draft; everyone else stays on the version that was published.

The problem this solves

Editing a live tool used by a whole team is normally a choice between disruption and paralysis.

Layout changing under someone mid-task
A half-finished redesign visible to the whole company
Builders afraid to touch anything during working hours
Experiments deferred to evenings and weekends

How the two views differ

User	What they see
Builder with build mode on	The draft version being edited
Builder with build mode off	The published version, as members see it
Member	Always the published version

How to work with it in Jestor

Pin the stable version as published in Jestor, switching off auto-publish.
Edit with build mode on — your changes accumulate in a new version.
Turn build mode off to preview exactly what members currently see.
Confirm the published version is the one you intend before ending the session.
Publish the new version when it is ready.

Why choose Jestor for live app maintenance?

Jestor ties the preview to build mode rather than to a separate environment, so checking what users see is a toggle instead of a deployment.

Members cannot reach the draft version at all, which means an unfinished change is genuinely invisible rather than merely unlikely to be found.

Frequently Asked Questions

Can members see my draft?

No, they only ever see the published version. See jestor.com.

How do I preview what they see?

Turn build mode off.

What if I forget to publish?

Users stay on the pinned version until you do.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,