01 / your computer
App + simulator + console
The app uses production code. A local simulator supplies responses and synthetic account data, constructed to mimic production.
internal product tool · fintech
The production app, on your computer. Explore the installed production release with test accounts you control: follow flows, use the app and inspect its activity in one workspace.
01why it exists
To look at one screen for one kind of customer, a product manager used to need a QA account in exactly that state, a test phone, and usually someone from engineering to set both up. Questions like “what does a customer two days past due actually see?” took a day to answer, so they often went unasked.
Honest MOCK runs the production Android app on a Mac or Windows PC against a simulator that stands in for the company’s backend. Choose a customer type and the account is rebuilt in seconds. Follow a journey screen by screen, use the app, watch what it sends, and move the calendar forward to see what happens next.
It is rebuilt each week from the release customers have, so it never drifts from the product.
02a guided look
Eight features. Select any screenshot for a closer look.
01 / Workspace
Setup, Flows, Emulator and Inspector work together or on their own.
1 of 8
03getting started
One plugin from the company’s marketplace, on a Mac or a Windows PC.
It installs the emulator and the tools it needs, and downloads this week’s ready-made app.
Each step is explained in plain language. You type the passwords and press the sign-in buttons yourself.
The first visit opens the how-to guide. From then on it updates itself with each release.
04how it works
The app, the simulator and the console run on your computer. There is no connection to QA or production backends.
01 / your computer
The app uses production code. A local simulator supplies responses and synthetic account data, constructed to mimic production.
02 / the landing page
The internal site serves a static page. Your browser shows the local console inside it; console data never reaches the site.
03 / releases
A maintainer builds from the production release. Each computer checks a release’s signature before installing it.
05decisions
06questions, answered
The QA app tests whether a build works. Honest MOCK shows what production looks like and does for a given customer, for people who are not engineers. QA keeps its time for releases.
Production’s own code runs. Only the network layer points to the simulator, which answers with production’s fields, types, enum values and error codes, taken from the app’s schema and each service’s code. Vendor SDKs (card security, the face check, pushes, feature flags) get stand-ins.
The starting point is the app team’s own mock responses. Values such as balances, limits and fees follow production totals and averages. A value production does not make clear stays unknown. The weekly drift report lists the calls with no answer yet.
Only what you can do. It never stores a key or token in a repository, it keeps its files in two folders, and it asks before accepting licences, scheduling the weekly sync, pushing or publishing.
That week’s release is late. Everyone keeps the previous release; the tool is not business critical. A new maintainer makes a release key and adds it by a reviewed change.
Storage for the current release and the last four on a shared drive. The landing page is static and scales to zero. Builds run on the maintainer’s Mac. AI tokens are used only for set-up, the weekly sync report and prototype changes; the console, the emulator and Flows use none.
[built at Honest, where it is an internal tool · synthetic test data throughout · not available outside the company]