- Existing Evidence
- Source-linked scenes, pose editing, color keyframes, clip audio, and video export work in one native app. The reported checks cover saving, reopening, scripted edits to the open project, and exported output.
- Relevant to Your Project
- A specialized production tool where inputs and revisions need to stay connected to the finished output.
- A Useful Acceptance Check
- Define one representative project and check editing, saving, reopening, and the exported result.
Tools PhreeLabs Needed,
So It Built Them
Eight products built for PhreeLabs’ own work (a video-creation app, a game engine, the authoring app made for it, a marketing decision app, and apps for client projects, content production, research, and verification) and the studio’s own website. None of them is a client commission.
- 01 Build for the Studio’s Work
- 02 Make the Capability Inspectable
- 03 Apply It to Your Brief
The products give PhreeLabs a place to develop and examine its engineering approaches. Commissioned work starts from your requirements; the lessons can inform future in-house research and development. Each project’s deliverables and ownership follow its agreed scope.
Products and the Studio Website

Explainer Studio
Source-linked animated explainers, with editable poses, color animation, mixed clip audio, and video export.
View Project
Webs
A 2D platform-fighter engine with buffered attacks, guards, throws, and motion commands, plus rules you can edit mid-match.
View Project
Architect
From PNG artwork to a playable Mac game, with menu audio, saved settings, throw authoring, and tests on the real engine.
View Project
MarketHaven
Marketing decisions, reviewed drafts, a publish queue, and outcome measurement, with approval tied to the exact content and its receipts.
View Project
AptitudeGrove
Client projects kept in writing, with what is waiting on whom always visible.
View Project
WovenLogic
Campaign assets built from one brief, with every out-of-date version flagged.
View Project
FixationNook
Claims tied to quoted evidence, with repeated sources counted once.
View Project
ProofRivet
Claimed, tested, and accepted kept apart, with checks run on a recorded build.
View Project
phreelabs.com
The site you’re on: designed and built by PhreeLabs for itself. Checked at phone, tablet, and desktop widths, with an inquiry form that delivers to the studio’s inbox.
See the Case ExampleEach project page connects the working features to the design, architecture, and test evidence behind them. The proposed addition to Architect is on Coming Next.
What the work
can do for yours.
These in-house builds show engineering approaches you can inspect. The application to your business is a starting point for scoping; the project needs its own requirements and validation.
- Existing Evidence
- A native Mac shell brings together editing workspaces and the Webs runtime, then packages a playable game. Menu audio and settings that survive relaunch have been checked in packaged games.
- Relevant to Your Project
- An internal application that needs a usable interface over existing processing or a specialist engine.
- A Useful Acceptance Check
- Agree on the data contract and validate the handoff between each layer, including rejected input.
- Existing Evidence
- A documented renderer investigation isolated repeated one-second stalls; a subsequent 120-input run recorded none in 597 frames.
- Relevant to Your Project
- Software rescue where a visible symptom needs a measured diagnosis before choosing the repair.
- A Useful Acceptance Check
- Reproduce the problem, record the conditions, then repeat the same check after the change.
- Existing Evidence
- Campaign inputs, reviewed assets, content approvals, receipts, and recommendations share one local record. Controlled provider fixtures exercise both approved actions and the actions the app must refuse.
- Relevant to Your Project
- A review or decision tool where people need to trace an output back to its inputs and judge the evidence behind it.
- A Useful Acceptance Check
- Use known inputs to check the calculation, missing-data behavior, and the explanation shown to the person deciding.
The product pages show their development status, engineering evidence, and test conditions. For website delivery, see the studio site’s case example.
See Illustrative EngagementsHave a Problem
Like These?
Describe it. A free written project discussion starts with what the software or site needs to do.