This is the free version of this report, exactly as a free audit shows it. 22 more findings are in the full report. Read the full report →
Clarity before change.

Independent website review

MyBishBash Photobooth

Website review

A full source-code and hands-on review of what MyBishBash Photobooth (our own product) ships, says and asks visitors to do.

Key judgement

The engineering here is excellent: the rendering engine, the consent design and the pricing setup. The next step is to connect it to revenue: a working way to pay, a way to get in touch, and a clear message for free users.

Overall view · At risk

https://raes-photo-booth.vercel.app/

Inspected 9 August 2026

Full review of the code and the live product (our own product)

What we noticed

A clearer view of what the website is doing now.

A GreatInternet review of what MyBishBash Photobooth says, shows and asks visitors to do:based on full source access and hands-on sessions: it is our own product, reviewed to the standard we sell.

Illustrative sampleWebsite Health Check view

What we looked at

Full-access audit: full source review (38 files, ~17,986 lines) plus hands-on sessions in the live product at desktop and mobile viewports as a first-time anonymous visitor, completed 9 August 2026. This pack translates that audit into our standard report contract; it is dated and presented as an assessment as of 9 August 2026, not a re-audit of the product as it stands today. Sample pack authored under our own methodology, the same one we sell: it is our own product, reviewed to the same standard as a customer's.

The short version

MyBishBash Photobooth is a genuinely good product with no working way to pay for it, no working way to contact anyone about it, and no way for a free user to be told why the thing they just spent five steps configuring did nothing. The rendering engine, the consent architecture and product.js are better than most funded products at this stage. The commercial layer is the problem, and it is not one bug: every paid tier dead-ends, every Business contact route 404s, and a completed free setup saves nothing.

The engineering here is excellent: the rendering engine, the consent design and the pricing setup. The next step is to connect it to revenue: a working way to pay, a way to get in touch, and a clear message for free users.

The first useful move

Reconnect the contact mailto:, decide the checkout state, and stop the silent save from discarding a user's work, in that order, roughly a day of combined effort.

Overall signal

A directional view, not a grade.

Genuinely excellent engineering craft (imaging, consent architecture, and product.js's price/capability separation all score 9/10 in the source audit) sits on top of a commercial layer that currently converts zero: every paid tier, every Business contact route and the free-to-paid save action are all disconnected, and the site sells to UK consumers with no terms or privacy policy.

Overall view: at risk

What would strengthen it: Reconnect the three commercial exits (contact, checkout state, silent save) and publish terms/privacy/refund: both are scoped as near-zero-risk, independent of the planned domain migration, and mostly already specified in the source repository's own implementation tracker.

Significant evidence indicates this area may undermine customer confidence, outcomes, or business performance.

Three things that are already working

  • ✓ product.js is the quality benchmark in the repository: 802 lines, zero dependencies, deep-frozen throughout, with prices and capabilities structurally separated so a price edit cannot widen access.
  • ✓ The consent architecture correctly separates marketing and publicity permission, requires the exact wording and its version in every consent record, and never infers consent from an email address.
  • ✓ The rendering engine is a documented pixel pass: including a written record of a Safari-17 filter regression and its fix, which is exactly the institutional memory that stops it being "simplified" back later.

The useful diagnosis

Biggest opportunity and biggest risk

Biggest opportunity

[F-01, source severity Blocker] Every paid tier says the shop is shut

Clicking any of the three paid plans renders "This service is not available yet." with class checkout-status error. curl to /v1/plans returns 404, identical for all three plans.

Directly reproduced live and confirmed by a same-day curl check of the billing endpoint.

Biggest risk

[F-02, source severity Blocker] The Business funnel has no contact route at all

All four "TALK TO US" CTAs resolve to https://mybishbash.app/contact, which returns 404. Site-wide there are zero mailto: and zero tel: links.

Directly confirmed by curl across all four CTA locations; the domain itself is live, isolating the fault to this one path.

Additional legacy finding

[F-03, source severity Blocker] Customise My Booth silently discards a free user's work

Completing all five steps of the Customise My Booth flow and clicking Save produces no visible message and writes nothing to localStorage.

Directly reproduced live with a concrete before/after localStorage check.

Additional legacy finding

[F-04, source severity High] One Safari-flavoured alert for six different camera failures

Clicking START PHOTOBOOTH with the camera unavailable fires a native dialog reading "Please allow camera access in Safari and try again.", regardless of the actual cause.

The failure and its cause are directly evidenced in source; the in-app-browser behaviour itself is explicitly [verify by hand] in the audit, since the audit browser cannot reproduce in-app browser restrictions.

22 more findings in the full audit.

One immediate recommendation

  1. 01

    Reconnect the three disconnected commercial exits (contact, checkout, and the silent save) before any other work.

  2. 02

    Publish terms, privacy and a refund notice before the first live transaction.

  3. 03

    Reprice Personal around the event, not the subscription duration, and show the real free-vs-paid difference on the pricing card.

More of this report

Go deeper only when it is useful.

Full website audit

Complete findings, evidence, strengths, and what to leave alone

Website Review & Implementation Pack

Website Review & Implementation Pack

The complete Website Review & Implementation Pack: annotated evidence, accepted findings, master plan, numbered work packets, tracker, Decision Register and verification materials.

Website Review & Implementation Pack

Strategic review

A human-led Founder Strategy Review: pre-call hypotheses, consultation, Founder Decision Memo and decision-execution tracker.

Founder Strategy Review

Purchases are temporarily unavailable.

Your current report remains available. Please return later to unlock more sections.

This report continues

What the full report adds

The assessment behind this document is complete. The sections below were produced from the same evidence and are held at a higher access level.

Full website audit

Website Review & Implementation Pack

Complete findings, evidence, strengths, and what to leave alone

Website Review & Implementation Pack

Website Review & Implementation Pack

The complete Website Review & Implementation Pack: annotated evidence, accepted findings, master plan, numbered work packets, tracker, Decision Register and verification materials.

Strategic review

Founder Strategy Review

A human-led Founder Strategy Review: pre-call hypotheses, consultation, Founder Decision Memo and decision-execution tracker.

Methodology & transparency

Methodology, transparency & limitations

This report has been generated with the assistance of artificial intelligence using the evidence available at the time of assessment. GreatInternet applies a defined assessment methodology and presents observations, judgements and recommendations based on that evidence. AI-assisted output should be reviewed by an appropriate human decision-maker before material reliance or implementation.

Limitations

  • The camera flow (three-shot capture, strip/cover/Polaroid rendering, iOS Share fallbacks) was never exercised (the audit browser cannot be granted camera access) and is assessed from source only. No finding here claims the capture engine itself is broken.
  • The Worker (billing, entitlement, Business API) is not deployed; /v1/* returns 404 on the live origin, so that entire layer is audited as-coded, not as-running.
  • Since this audit (9 Aug 2026), the source repository's own implementation tracker (WORK.md, last updated 2026-08-11) records packets landed against several findings here: PB-01 (F-02, contact mailto wired), PB-02 (F-01, dead-checkout messaging made honest, purchases still cannot complete; BILLING_LIVE remains false), PB-03 (F-03, silent save fixed), PB-05 (F-05/F-06, origin constant and social metadata added), PB-06 (F-17, demo image reduced), PB-07 (F-07/F-08, robots/sitemap/branded 404 added), PB-08 (F-21, mobile nav fix), PB-09 (F-04, camera error branching), PB-10 (F-24/F-25/F-26, accessibility gaps closed). This document does not mark any of these findings resolved: doing so would assert a retest of the live product that this pack did not perform (see the file-level comment in photobooth-sample-report.ts for why). Findings F-09, F-10, F-13, F-14, F-15, F-16, F-19, F-20, F-22, F-23 have no corresponding completed packet as of that tracker entry.
  • Two live defects were found by the source repository's own later work (PB-17, PB-29) that this 9 Aug audit did not itself identify: a silent gallery-trim bug past 20 sessions, and a /business/ trailing-slash routing failure. Neither is a finding in this document, since this pack translates only the 9 Aug audit.