Creator submissions
Prepare safer, clearer AI-made web works for review and publication.
oeeco Blog
Notes on AI-made web works
Field tests, case studies, editing notes, and practical publishing guides for people building browser games, interactive tools, visual experiments, and small software artifacts with AI-assisted workflows.
Start here
Explore by topic
Follow the main oeeco themes: field-tested tools, playable games, product craft, publishing, and trustworthy review.
Browser games
Learn what makes small AI-assisted games playable, readable, and worth replaying.
Interactive tools
Turn prompts and workflows into useful browser tools people can test on their own material.
Review and trust
Understand oeeco's publishing standards, safety expectations, and editorial approach.
Case studies
Detailed editorial reviews of specific AI-made games, tools, and browser experiments on oeeco.
Product craft
Design better inputs, trials, failure states, mobile behavior, and data boundaries for small web tools.
Publishing and operations
Prepare, describe, release, monitor, correct, and maintain a public browser work.
Visual experiments
Review generative canvas tools, visual controls, export behavior, and the images used to present interactive work.
Editing Notebook
Read articleThe Sentence Sounded Fine. That Was the Problem.
An editing notebook on replacing generic AI cadence with observations, uncertainty, concrete nouns, and accountable editorial judgment.
Orbital Salvage Case Study: A Deeper AI-Made Browser Game
An editorial case study of Orbital Salvage, focusing on physics feel, recovery goals, failure feedback, and why a small AI-made game can feel substantial.
Customer Interview Signal Lab: Editorial Review of an AI-Made Research Tool
A practical review of Customer Interview Signal Lab, an AI-made browser tool that turns messy interview notes into product evidence, themes, and next questions.
Landing Page Copy Doctor Review: A Useful AI-Made Messaging Tool
A case study of Landing Page Copy Doctor and what it teaches about narrow AI-made tools, practical outputs, and honest copy review.
One Button Dodge: A First-Minute Review of a Tiny Browser Game
A close review of One Button Dodge and how a very small AI-made game can teach controls, feedback, failure, and replay in the first minute.
Micro SaaS Validation Lab Case Study: Turning an Idea Into Testable Risks
A case study of Micro SaaS Validation Lab and how AI-made browser tools can help founders map risk, audience, pricing, and next experiments.
Three Topics Through the AI Prompt Card Generator
A hands-on test of the AI Prompt Card Generator with a game, a tool, and a visual experiment, including what its template clarifies and what it cannot decide.
We Compared 12 Mutations of One Product Idea
Workshop notes from running a meeting-notes product through four Idea Mutation Machine settings and comparing the 12 resulting directions.
Evo Colony and the Difference Between Activity and a System
A design teardown of Evo Colony: how visible rules, delayed consequences, and readable state turn a moving simulation into something a visitor can reason about.
Mood Garden: Can a Gentle Visual Tool Still Have Clear Controls?
An interaction critique of Mood Garden, looking at emotional labels, sliders, animation, export, and the risk of confusing atmosphere with usability.
Neon Poster Maker Under Three Real Briefs
A test of Neon Poster Maker with a game launch, a community event, and a product update, including where typography becomes fragile.
A Launch Checklist Is Only Useful Before You Feel Ready
A candid walkthrough of using Tiny Launch Checklist on a nearly finished browser demo, including the high-scoring gaps that were easy to postpone.
The 12-Minute Review: How We Read a Small Web Work
oeeco's time-boxed method for reviewing a small browser work, from first impression and core action to failure, trust, and the listing decision.
Sample Data Is Part of the Product, Not Placeholder Copy
Why good sample inputs teach an AI-made tool's scope, expose its reasoning, and let a visitor judge value without handing over private material.
Let People Try the Smallest Useful Thing Before Login
A practical argument for guest trials in AI-made web tools, with boundaries for saving, exporting, rate limits, and account creation.
The Output Is Empty. Now What? Designing Failure States for AI Tools
A failure-state field guide for AI-made tools: empty input, weak evidence, timeouts, partial results, unsafe requests, and recovery without blame.
A Phone Is Not a Smaller Desktop: Mobile QA for Interactive Works
A hands-on mobile QA routine for browser games, canvas experiments, and AI-made tools, focused on controls, keyboards, safe areas, orientation, and recovery.
Before You Add a Database, Ask Whether the Browser Is Enough
A guide to local-first design for small tools: what can stay in the browser, when a backend earns its complexity, and how to explain the boundary.
We Rewrote Six Web-Work Descriptions. Here Is What Changed.
Six before-and-after edits showing how to replace vague AI language with concrete inputs, actions, outputs, constraints, and honest reasons to try a web work.
Choose the Frame That Explains the Work
An editorial guide to cover images for games, tools, and visual experiments, with a five-frame contact-sheet method and common misleading choices.
Seven Things That Pause an oeeco Review
Concrete editorial red flags that stop a work from moving forward, why each one matters, and the evidence that lets review resume.
A Seven-Day Polish Sprint for a Small Web Work
A day-by-day release plan that improves one core loop, tests real states, tightens the listing, and ships without turning a small work into a platform.
The Quiet Page Every Web Work Needs: A Maintenance Ledger
How to keep a small public work trustworthy with a lightweight ledger for deployments, dependencies, links, known issues, corrections, and ownership.
What Are AI-Made Web Works?
A practical definition of AI-made web works: playable browser games, useful tools, interactive experiments, and small shipped products made with AI-assisted workflows.
How Codex Changes the Way Small Web Games Are Built
Small browser games are a natural fit for AI coding agents because the loop is visible, testable, and easy to improve through quick iteration.
Why Interactive Tools Are Better Than Static AI Demos
Interactive tools turn AI-assisted ideas into useful workflows that visitors can test, repeat, and share instead of passively reading about them.
How to Submit an AI-Made Web Work to oeeco
A practical guide to preparing a clear, safe, and useful oeeco submission with the right title, summary, tags, demo URL, and creator context.
What Makes a Good AI-Made Browser Game?
A checklist for small AI-assisted browser games: clear loops, readable controls, fair feedback, mobile awareness, and enough polish to invite another run.
How to Turn a Prompt Into a Playable Web Tool
A workflow for turning an AI prompt idea into a useful browser tool with inputs, outputs, constraints, examples, and a shareable page.
Why AI Creators Need Public Portfolios
AI-assisted creators need public, inspectable portfolios because shipped links show judgment, taste, iteration, and reliability better than prompts or screenshots.
The Difference Between AI Demos and Shipped Web Works
AI demos prove a possibility, but shipped web works create a usable artifact with context, reliability, safety, and enough finish for real visitors.
A Checklist for Publishing Safe Interactive Web Projects
A practical safety and quality checklist for publishing browser-based AI-assisted games, tools, and experiments that visitors can open with confidence.
How oeeco Reviews AI-Made Works
A transparent look at how oeeco thinks about reviewing AI-made games, tools, interactive pages, and experiments before they become public.
Best AI-Made Browser Games to Study
What creators can learn from small AI-assisted browser games: focused loops, readable feedback, tuned controls, and lightweight publishing.
How to Review an AI-Made Web Tool
A practical review framework for AI-made browser tools: purpose, inputs, output quality, safety, repeat use, and honest limitations.
AI Web App Publishing Checklist
A pre-publish checklist for AI-assisted web apps covering purpose, safety, metadata, mobile layout, performance, policy pages, and post-launch review.
Examples of Useful AI-Made Tools
Examples and patterns for useful AI-made browser tools, from interview synthesis to validation labs, prompt workflows, and copy diagnosis.
How to Make a Small Web Game Feel Finished
Small web games feel finished when they have a clear start, readable controls, fair failure, polish through restraint, and a smooth restart loop.
Common Mistakes in AI-Made Web Work Submissions
The submission mistakes that make AI-made projects harder to review: vague titles, unsafe links, thin descriptions, missing context, and broken first interactions.
Design the First Minute of an AI Browser Game
The first minute of a browser game should teach the goal, controls, feedback, failure, and restart loop without making the player read a manual.
How to Design Inputs for AI-Made Web Tools
Useful AI-made tools start with realistic inputs: messy notes, rough ideas, concrete constraints, and clear examples that help visitors get a better output.
Trust Signals for AI-Made Content Sites
AI-made content sites need visible trust signals: author context, policy pages, review standards, safe links, contact routes, and original useful pages.