Make it feel fair.
The shield you see should be the shield the game actually uses.
AN INDEPENDENT SCREEN REVIEW / 01
A better start,
by design.
A closer look at your workspace setup screen—and a more considered, single-file rebuild.
3,106original lines reviewed
13findings documented
01file to replace
THE BRIEF Preserve the contract. Fix the edges. Make the first interaction feel considered.
FIG. 01 / THE SCREEN STUDY INTERACTIVE
FORM01 — 02
9:41▮▮ ▰
✳ PolyVision↗
WORKSPACE ACTIVATION
Set up your
admin workspace.
Create a workspace for your team, then choose how to activate it.
✓Workspace
2Activate
Company detailsYour team workspace name.
✓COMPANY / TEAM NAME
✓ Workspace created
Activation paymentChoose a plan, or try the challenge.
Step 2 of 2 · Browser study only
OPS DEFENSE / DEMO1 Month challenge
YOUR SCORE0
COMBO1×
SHIELDS● ● ●
DRAG TO MOVE
WEB DEMO · NO REWARDS OR PAYMENTS
SCREEN01 / 01
01 A quieter way in.SELECT A PLAN OR PLAY ↗
THE WHOLE SCREEN, NOT JUST THE SURFACEREVIEWED END TO ENDEXISTING CONTRACT RETAINEDNO NEW APP FILES
01 / THE REVIEWTHE SHORT VERSION
Good first impressions
need good foundations.
This screen does a lot: creates a workspace, handles payment, runs ads and hosts a game. The details behind each of those moments matter just as much as the interface.
Download the full analysis ↗Protect the moment.
One checkout at a time, with a safer route back from failed confirmation.
Leave room to leave.
Pause, resume and exit without losing control of the screen.
Keep the seams.
The existing imports, endpoints and public screen contract stay in place.
02 / FIELD NOTES
What was
actually wrong.
Not a list of cosmetic tweaks. Each note traces a behavior back to the original source and explains what changed—or what still needs work elsewhere.
LINE NUMBERS REFER TO THE ORIGINAL FILE
Read all review notes ↗FINDINGPRIORITY / SOURCE
13 FINDINGSSELECT A ROW TO READ THE DETAILS ↓
THE ENTIRE FILE / 01All 3,106 lines, in context.Open the section-by-section source map＋
L1–95
Imports & plans — Public type, static prices, native ad guard and existing dependencies establish the integration boundary.
L96–241
Motion & haptics — Animation and loading feedback had duplicate Android vibration and retained completed timer handles.
L245–280
Theme tokens — String ordering was used as luminance and alpha was appended to arbitrary colors.
L282–425
Game definitions — Entity types, pool and fixed screen geometry determine what can spawn and where.
L428–581
Arena rendering — The scaled paddle pivot did not match its logical collision bounds.
L583–1111
Simulation & ads — Launch, pooled spawns, animation, collisions and timers contained the major game lifecycle risks.
L1113–1816
Game interface — HUD and result overlays had no pause/exit path during play and lacked a Chrono timer.
L1819–2075
Stepper & cards — Reusable controls included a null-only error component and limited selection semantics.
L2077–2661
Screen & transactions — Store hydration, registration, rewards, checkout, linking and the main UI meet here.
L2663–3106
Styles — Theme-derived colors, legibility, shadows and layout complete the screen.
03 / LOOK CLOSER
A small shift.
A different game.
Aegis scales the paddle from its center. The original hitbox grew from the left edge instead. At full width, the two are off by 12.88 pixels on each side.
Move the control to see the mismatch—and the corrected alignment. The diagrams use the original 92 px base width.
Visible shield Collision bounds
INTERACTIVE / PADDLE BOUNDSORIGINAL L540–555
01 BEFOREVISUAL ≠ HITBOX
02 AFTERONE SHARED LEFT EDGE
ORIGINAL OFFSET12.88 px→REPLACEMENT OFFSET0 px
03B / THE CODE CHANGESBEFORE & AFTER · EXCERPTS
Small changes.
Clearer behavior.
Three examples from the rebuild. These are abbreviated excerpts; the complete implementation is in the source below.
BEFORE / ORIGINALL540–555, L970–971
AFTER / REPLACEMENTONE SHARED MODEL
04 / THE ITERATIONSRATED HONESTLY
Better takes
more than one pass.
Four rounds of refinement, with the hard problems addressed before the polish.
CURRENT REVIEW ESTIMATE8.8 / 10
10 is the target, not a claim.
005.2
Baseline
Ambitious scope, but several game and checkout edge cases.
ORIGINAL016.6
Define the seams
Preserve the contract; remove unsafe colors and dead UI.
FOUNDATION027.6
One clock
Unify movement, collision, pause, bounds and pool behavior.
SIMULATION038.4
Guard the money
Lock actions and make in-session confirmation retryable.
CHECKOUT048.8
Test the seams
Strict mock type-check, math checks and behavioral tests.
CURRENT PASS05 / THE HANDOFFKEEP THE CONTRACT
One file in.
No new dependencies.
The replacement is designed for the existing screen boundary. It retains what the rest of the app expects, while keeping the limitations visible.
01
Public surface
RETAINEDDefault TenantSetupScreen export and PlanItem shape preserved.
02
Existing services & stores
RETAINEDSame relative imports, auth/offline selectors, theme, ads and tab-bar hooks.
03
API boundary
RETAINEDExisting registration, plans, reward, order and verify endpoints and payload keys.
04
Packages & app files
ONE FILENo additional package or change to another application file is required by the replacement.
05
Type check & behavior
MOCKEDStrict TypeScript against mock declarations; math and component behavior exercised with mocks.
06 / THE COMPLETE FILEREAD IT. COPY IT. MAKE IT YOURS.
The work,
in full.
Everything in the replacement is here. Search the file, jump to a section, copy it or download it directly.
07 / BEFORE YOU SHIPTHE LAST MILE
A thoughtful finish
needs a real-world test.
Put the file in place, then verify the parts this workspace cannot see.
Get the integration checklist ↗- 01Replace the screen
Back up the original and replace
src/screens/auth/TenantSetupScreen.tsx. - 02Build and exercise the real app
Test checkout, ads, interruption, orientation, accessibility and performance on actual devices.
- 03Verify the server boundary
Confirm payment signatures, idempotency, durable reconciliation and authoritative reward eligibility.