Game Economy Simulator →
Game QA Matrix →Digital Products
Downloadable and software products with explicit delivery terms.
Products built to solve real problems.
Arcade Lab — interactive tools
Try two free, working game-development utilities and browse their supporting research-oriented guides.
A catalog for verified digital products, tools and future physical offerings produced by the Factory.
MOJPLAYWIN / CURATED
Business Tools
Practical tools for costing, workflow, research and productivity.
New Products
New categories appear only when the Factory has a real product to offer.
What makes a digital product ready for customers?
A serious digital product is more than a download. Give it a clearly defined audience, practical outcome, file formats, supported platforms, installation instructions, sample preview and version number. For a technical toolkit, test with invalid inputs and document the assumptions of every calculation. For an e-book, check contents, fonts, internal links, page numbering, image legibility and accessibility.
Design fulfilment as a recoverable process: payment status is checked independently, download entitlements are scoped to an order, interrupted delivery can resume, and duplicate notifications do not create extra charges. State usage rights and realistic support limits. Do not publish an active Buy button until product identity, actual files, pricing, taxes where applicable and the complete customer path have been verified.
Apply this in three steps
- Have a new user complete the advertised task without help.
- Run checksum, accessibility and device compatibility checks.
- Test purchase, confirmation, delivery and refund-support scenarios in a controlled environment.
Key takeaway: The product is only ready when customers can reliably obtain and use the promised result.
Explore more free field notes →Publishing a professional digital book without quality defects
An effective digital book is a coherent learning experience and a reliable file. Page count does not demonstrate depth. Readers need clear chapters, accurate examples, legible illustrations, working navigation and an accessible download.
Working method
Separate manuscript review from production engineering. Check quotations and calculations, remove repeated explanations, link each exercise to its annotated solution and inspect images at reading size. For PDF, embed fonts, test bookmarks and links, check text extraction and examine reading order when accessibility is part of the audience's needs.
Worked example
A chess workbook can present a FEN position, a question, an expected thinking time, multiple plausible plans and an annotated answer. Showing the solution on the same page as the exercise may spoil the learning objective. A file checksum confirms binary integrity, not the correctness of tactical analysis.
Common mistake
Do not claim an advanced professional standard without subject-matter and editorial verification.
Action checklist
- Check learning objectives and originality.
- Test diagrams, metadata, links and mobile readability.
- Verify actual customer downloads before sales.
Release notes, versioning and support for small software products
Even a simple downloadable spreadsheet or standalone tool needs predictable updates. Customers should know the version, compatible platforms, limitations and a safe route to recover if an update changes behavior.
Working method
Use an explicit version number and maintain a changelog describing fixes, changes and breaking differences. Create test fixtures for old file formats and representative inputs. Publish checksums and give realistic support expectations. Keep experimental changes separate from stable calculations and document data migrations.
Worked example
For a farm budgeting workbook, version 1.1 might add an orchard scenario while preserving the core contribution-margin formula. A regression test should reopen a version 1.0 sample and compare units, input cells and calculated outputs. Release notes should distinguish a new feature from a corrected calculation.
Common mistake
Do not silently replace a file under an unchanged version identifier. Traceability and reproducible packages reduce customer confusion.
Action checklist
- Version the release and its documentation.
- Run compatibility regression tests.
- Publish clear changelog and recovery instructions.
Licensing downloadable tools without punishing legitimate customers
A digital product license explains what the purchaser may do with a file, template or program. Good terms distinguish personal use, commercial deployment, redistribution and access to updates. The technical controls should enforce the actual license without creating unnecessary lockouts.
Implementation method
Describe the number of permitted users or installations, supported formats and how replacements work. Link entitlements to a verified order and provide a secure way to recover access when a device changes. For software, avoid embedding permanent privileged secrets in client-side files and disclose any activation service dependency.
Applied example
A company might sell a planning template for one internal business team. The license can permit multiple employees inside that team but prohibit reselling an unchanged copy. A download token should expire safely and be renewable through authenticated order history. Revoking legitimate access after a temporary network outage would damage customer trust.
Important limitation
Licensing and copyright law vary across jurisdictions; publish clear terms and seek appropriate review for consequential contracts.
Action checklist
- Write plain-language allowed and prohibited uses.
- Test account recovery and device changes.
- Align download controls with the published entitlement.
Evaluating subscription retention before scaling acquisition
Recurring revenue is not automatically durable revenue. Acquisition cost, cancellation reasons, payment failures and product usage all affect whether a membership offering works. Evaluate retention by signup cohort and distinguish voluntary cancellations from accidental payment failures.
Implementation method
Define a clear membership promise, recurring billing interval, renewal notice, access rules and cancellation process. Analyze how many members remain active after the first and third renewals. Review what customers actually use, not only which features were advertised. Forecast support, infrastructure and content costs alongside receipts.
Applied example
If 200 customers begin a monthly plan and 150 remain paying after three months, cohort retention at that point is 75%, assuming the cohort definition stays fixed. That percentage alone does not reveal acquisition cost or profitability. A low-priced membership with frequent expensive support requests can have weak contribution margin despite healthy headline retention.
Important limitation
Do not make cancellation obscure or imply membership revenue is guaranteed.
Action checklist
- Describe an honest subscription value proposition.
- Track retention by original signup cohort.
- Model refunds, failed renewals and support expense.
NEW INTERACTIVE TOOL
Frame Budget Lab
Estimate CPU and GPU timing, compare frame-rate budgets and export your scenario to CSV or JSON.
Launch Frame Budget Lab →
NEW FREE INTERACTIVE TOOL
Image Delivery Lab
Convert images into real WebP variants locally, compare actual bytes, download optimized files and copy accessible responsive HTML. No upload or account required.
Open Image Delivery Lab →New: 50 practical game-production guides
Read independent, source-linked implementation notes covering performance, responsive assets, touch controls, accessibility and browser security. Includes a new free laser puzzle game.
Browse 50 original field guides →