Kwark. Design System
Open Kwark

Inclusive design

Who Kwark is for, what each of them stands to lose, and how Kwark decides on their behalf: students from 13, cheap phones on slow networks, offline work, many languages, calm for every kind of mind, privacy and cost.

Foundations

Your work

No saved changes recorded here yet

Saved on this device

Decide for real people, in their real situation

Inclusive design at Kwark is not a list of edge cases. It is the main case. The people Kwark is built for include a 14-year-old writing a first short on a school laptop, a crew member reading a call sheet on a five-year-old Android phone in a field with one bar of signal, an actor whose lines are in Tamil, a writer who can only work after the day job ends, and someone who finds a flashing badge hard to ignore.

Every decision that touches people runs through the same questions, taken from How we decide:

Question Asked of a change
Who is affected? Name them: the student, the actor, the crew, the owner. Not “users”
What were they doing a minute ago? Writing, travelling to set, on a break at work
What are they afraid of right now? Losing work, being judged, being seen, running out of data
What do they lose if we do this? Calm, privacy, time, data allowance, money, the ability to undo
What do they lose if we do nothing? The honest answer, written down
What is the smallest thing that helps? Build that first
What can they not undo? Design that part twice

The default rule. Anything that nags, counts, notifies or watches is off by default and lives in Settings, where a person can find it and turn it on for themselves (Decision 0008). Anything that protects work or privacy is on by default. When in doubt about which side a feature falls on, it is the first kind.

Students from 13

Kwark serves students aged 13 and above, including students under 18. That is confirmed, and an 18-and-over workaround is not the plan. Under-13 accounts are outside the first version.

What this changes in design:

  • Private by default, always. No public profile, no student directory, no public counts. New collaborators join as Readers and the request link is off until the owner turns it on (Decision 0042). A student cannot become publicly findable by using Kwark.
  • No social and no ranking. Competitions, leaderboards and feeds belong on Bekwarky, not here (Decision 0001). Teenagers already live with enough comparison.
  • Plain words, not childish ones. Write for a bright 14-year-old and a working producer at the same time: short sentences, correct film words, no slang, no jokes. The same wording serves both.
  • No teaching inside fields. Structure, not coaching (Decision 0004). A student learns the call sheet by making one that a crew can use.
  • Consent is designed, not assumed. The launch plan requires age and country checks before sign-in, a guardian route where the law needs one, and a working account option for students whose school blocks Google sign-in. That work is planned and gated; it is not built yet. Never design a screen that assumes it exists.
  • Never design a public surface, a directory or a “share to everyone” default that a student account could reach.
  • Never add profiling, targeted promotion or session replay.
  • Must treat cast and crew contacts, photos and child actors’ details as sensitive, whoever uploaded them.

Cheap phones and slow networks

Many of Kwark’s people work in India on mid-range and low-end Android phones, often on metered mobile data. Design as if every byte and every database read costs the person something, because Kwark’s own limits make it true for us too: the app runs inside Firebase’s free tier, about 1,000 reads and 400 writes per person per day.

  • One listener, shared. Never open a database listener per module, re-read a collection to redraw a list, or upload on a timer whether or not anything changed. The same discipline that keeps Kwark free keeps a person’s data plan intact.
  • Write the field, not the document. Field-path writes, change-gated background work.
  • Heavy things load late. 3D boards load three.js as a separate chunk only when a board is opened, and frames are baked to images so print, offline and the shooting book keep working.
  • No server image generation. The AI storyboard pack is exported for a tool the person chooses, partly because generating images on Kwark’s servers would cost money nobody has budgeted (see AI and authorship).
  • Phone layout is the first layout. Wireframes start at phone size. Content by about y = 200, one 44px header, 44px targets, one floating control (Decision 0016). The calendar opens on Agenda on phones because a time grid is unreadable at 360px (Decision 0043).
  • Small text is a cost. Nothing under 12px on a phone, nothing under 11px anywhere. Cheap screens are often dimmer and less sharp.

Kwark has not published measured load times or data use on low-end phones. Do not quote numbers until they are measured on a real device.

Offline is a normal state

A writer on a train, a crew on location and a student without home broadband are offline as a matter of course. Kwark treats offline as a state to describe calmly, not an error.

State What the person sees Where
All up to date Safe Corner sync word
Changes waiting for the cloud Safe here, waiting to reach the cloud Corner sync word
Working offline by choice Safe on this device (offline by choice) Corner sync word, after Work offline
Saved locally, no cloud claim Saved on this device Characters, Story locations
A write could not be stored The page stays open and offers Retry saving Characters
No connection when signing in We could not reach the internet. Your work is safe on this device; try again when you are back online. Sign-in

In production builds a service worker caches the app shell so Kwark opens without a network. A project that has never been opened on this device, with the cloud out of reach, opens read-only and never saves over anything.

  • Must describe the state in words and say the work is safe when it is.
  • Never block writing because the network is gone.
  • Never say failed, offline error or sync error (Decision 0013).

Many languages, many countries

  • Indian scripts in the script. A writer can give a character a language and type their lines on an English keyboard in Hindi, Marathi, Bengali, Tamil, Telugu, Kannada or Malayalam. The conversion happens on the device, from a fixed table; nothing the writer types leaves it. See Writing systems.
  • Bilingual scripts. Any line can carry a translation, and the Reader can show translations, or Devanagari in Roman letters for an actor who speaks Hindi but does not read it.
  • The interface is in English today. Localising the interface is not built. Write strings so they can be translated later: whole sentences, no words stitched together, room for text to grow by half.
  • Local forms. Money is written the way its own people write it: ₹12,50,000 for rupees, with eight currencies to choose from. Dates follow the device’s locale.
  • No single country’s paperwork. Unions, contracts, permits and crew rules differ by country. Never hard-code one country’s rules as the default, and never call a form “standard” when it is American.

Calm for every kind of mind

Some people find counters, streaks, badges, sudden movement or a crowded screen hard to ignore; for some it is the reason they stop. Kwark is designed so nobody has to fight the interface to write.

  • No streaks, no scores, no leaderboards, no “goal reached”. The rhythm widget lost its flame and moved off Home (Decision 0008), then was replaced by Your work, a private list of recently saved work with a link back to each, hidden until the person opens it (Decision 0036). Its empty state says No saved changes recorded here yet and never suggests the person has not worked: reading, rehearsing and working away from Kwark are real work.
  • Nothing interrupts thinking. The idle curtain that blanked the screen after 60 seconds was removed; it would have blanked a pitch or an animatic in a meeting (Decision 0012).
  • No notifications that exist to bring people back.
  • Predictable places. Five menus in the screenplay, always in the same order: File, Edit, Format, View, Help (Decision 0015). One floating control on a phone. The same word for the same action everywhere.
  • Motion only answers an action, and stops under reduced motion. No glows, no particles, no pulsing (Decision 0041).
  • Undo instead of fear. Prefer Undo to “Are you sure?”; deleting moves to trash.
  • Fewer things at once. Distraction-free mode (⌘⇧F) leaves the page. Structure is optional and leaves nothing behind when off (Decision 0003).
  • Time without guilt. The calendar can dim 9 to 5 for people with a day job, so evening writing blocks stand out, with no counters and no shaming (Decision 0043).

Privacy is inclusion

A person who cannot be sure their work is private cannot use the product fully. That is true for a student, for someone writing about their own family, and for anyone writing a story that would put them at risk if it were read too early.

  • Work stays on the device where it can. Indian-script typing, the calendar’s quick add and the breakdown’s suggestions all run on the device.
  • Kwark sends no email. After inviting someone, the sharing panel offers Copy invite message and Email them through the owner’s own mail app (Decision 0042). Kwark does not hold an address book.
  • Private first, shared on purpose. Research starts in a personal workspace; sharing a board or notebook moves it to Shared by team. Dailies says, honestly, when it is private to the person and on this device only (Decision 0043, Dailies).
  • Roles are about access, not identity. Answering “what do you do on a film?” in Dailies never grants or removes access to a project.

Cost is a barrier

Students and indie filmmakers have little money. Every design choice that costs Kwark money per person, or costs the person money, is a choice against them.

  • Prefer what runs on the device to what runs on a server.
  • Prefer an export to a tool the person already has (their mail app, their PDF reader, their chosen AI) over a paid service inside Kwark.
  • Never put a basic need (exporting your own script, printing a call sheet) behind a payment.
  • A free web app installable on the phone first is the launch plan’s recommendation, not a confirmed business model. Do not write prices or plans into the interface.

People who write at 2am

Screenplays are written over months, mostly at night, mostly by one person looking at the same rectangle. The editor’s rooms exist for this. Lamplight is described in the app as Warm brown desk, amber ink marks. Kind at two in the morning. Midnight is Deep blue with cool ink. Quieter than black without going cold.

  • At night, nothing should flash, glow or count.
  • Errors at 2am must be the calmest of all: the state, that the work is safe, and one thing to do.
  • Cmd+S still says Saved. Your script saves as you write., because a tired writer presses it anyway.

See Writing rooms.

Disability

Inclusion includes disability, and the detail lives on Accessibility: contrast in every room, a full keyboard map, screen readers, targets, motion, zoom and media. The rule here is simpler: a feature that does not work by keyboard, with a screen reader, at 200% zoom and on a phone is not finished.

How Kwark decides: worked example

Writing rhythm on Home (Decision 0008, then 0036).

Step Answer
Who is affected Every writer who opens Home, including first-time students
What they were doing Arriving to write
What they fear Not writing enough; being counted
What they lose with the widget Calm. A flame and Goal reached count them the moment they arrive
What they lose without it A private sense of rhythm, for the few who want it
The smallest thing that helps Keep it, private and quiet, off by default, in Settings. No flame, no streak, no resets. Remove the 60-second cloud sync, which also saves writes
What would make us remove it Almost nobody turns it on after a month
What happened next The day goal still measured attendance, and gave actors and crew nothing to do next. Decision 0036 replaced it with Your work: recent saved work by area and project, a link back, kept on this device, no totals, ring, target or congratulations

A rhythm that is off by default, private, quiet, in Settings, with a remove condition written down.

Do

A streak on Home that is on for everyone, resets after a missed day, and sends a reminder to come back.

Don’t

Safe here, waiting to reach the cloud while a crew member is out of signal, and the call sheet still opens.

Do

A red banner saying Sync failed and a spinner that blocks the page until the network returns.

Don’t
  • Must name who is affected and what they lose before proposing a change that touches people.
  • Must default to off for anything that counts, nags, notifies or watches, and to on for anything that protects work or privacy.
  • Must design the phone layout, the offline state and a slow network first.
  • Never add a database listener per module, a whole-document write for one field, or a timer where an event would do.
  • Never hard-code one country’s paperwork, currency or date format.
  • Never assume the guardian-consent or age-check flow exists in the app.

AI readiness test

Task. Design a reminder that helps a crew member arrive on time for Day 3 of the shoot.

Give the agent. This page, decisions 0001, 0008, 0013 and 0042, the call sheet pattern.

Constraint. Kwark sends no email and has no push sender; the crew member may be offline and on a cheap phone.

A reliable answer

  • Off by default and chosen by the person
  • Uses the person’s own calendar (an .ics they add) rather than a Kwark-sent message
  • Works offline once added
  • States the call time with the day and date in words
  • No counters, streaks or nagging follow-ups

Give this Markdown to your coding agent or share its URL.

Open .mdllms.txt
Loading…