Coloring app for young children: requirements, documentation and design

Doodle Meadow gives children a bright, simple space to color animals, food, and more, then keep their finished pictures in a gallery.

Book an intro call See the deliverables

Product name and branding changed to protect client confidentiality. Our role: discovery, requirements, documentation and design. We did not build it.

Screens designed: 52
Platform: iPad and phone
Market: Content needed: country or region
Our role: Discovery, documentation, design

Overview

Doodle Meadow is a coloring app designed for young children. Kids pick a category, choose a picture, and color it with markers, spray, and an eraser, then save it to their own gallery.

Parents manage the subscription, profile, and settings, with a sign-up step that unlocks the full library.

What made it complex

Designed for young children: simple tools and easy undo
Parents manage the subscription and settings, separate from the child's experience
A free tier, plus a sign-up step that unlocks the full library

Key decisions we made

Two or three decisions and whyFor example, a rule you simplified, a feature you cut from version one, or a trade-off the client accepted.

What the product does

Every feature below was specified in the requirements and shown in the designs.

Coloring categories. Animals, food, and more, each with its own pictures.
Coloring canvas. A full color palette with drawing tools.
Drawing tools. Markers, spray, and an eraser.
Undo and redo. Easy correction for small hands.
My gallery. Finished pictures saved in one place.
Unlock full access. Sign up to open the complete library.
Subscription. Manage the plan, profile, and payment method.
Help and support. FAQs, a contact form, and app rating.
Notifications. Updates on new pictures and features.

How we worked

Discovery sessions, then business, functional and technical requirements and a data model, then design and handover. Every screen traces back to a documented requirement.

The same process, as a service

What the client received

Plain names first; the short labels are what developers call each document.

BRD

Business Requirements Document

Business goals, users, scope, and success measures.

FSD

Functional Specification Document

Every feature, flow, business rule, and screen behavior.

TRD

Technical Requirements Document

Architecture, integrations, security, and performance requirements.

ERD

Entity Relationship Diagram

The data model behind the product and how its records connect.

Design

UX and UI design

52 screens, ready for development handover.

Pitch deck, if deliveredAdd as a deliverable where you prepared one for this client.

A look inside the product

5 of the 52 screens we designed. Scroll or swipe to see more.

Outcome

What happened nextOne true sentence, for example: the client selected a development partner, raised investment, or started the build. Remove this block if it cannot be shared.

52Screens designed

Content needed: a real quote from this client, two or three sentences, in their own words

Content needed: role, company type and country (name optional)

Have a product like this in mind?

We start with discovery: requirements, documentation and design that any development team can quote and build from.

Book an intro call

Free and without obligation. Content needed: call length

Before the callWe read what you sent, so the call starts with your problem.
On the callWe ask questions, listen, and explain how we would approach it.
After the callIf we are a fit, a written proposal with a fixed scope follows. If not, we say so.