K10 Creative
Design & development studio
000%
01 / Education technology
Thirty children, one teacher, forty minutes and a board on the wall. Most education software is designed for the demo, not for that room. We design for the room — the smart board, the tablets and the phones around it — and build the lesson so it survives a flaky school network and a Monday morning.
K–12 & higher ed
Schools, universities, publishers and course providers.
Pardus ETAP · Android · Windows
One codebase, every board in the building.
KVKK & GDPR
Student data handled as if it were your own child's.
02 / Platforms
The board is where the lesson happens; the rest of the week happens on everything else. We build the platforms that carry a class from homework to exam to report card — and make them feel like one product, because to a student they are.
A / Learning platforms
Course structure, assignments, grading and messaging in one place — shaped around how your school actually runs a term, not around a vendor's idea of one.
B / Assessment & exams
Question banks, timed exams, instant feedback and anti-cheat that respects students. Built to survive a whole year group logging in at nine sharp.
C / Mobile learning
Revision that fits in a bus ride. Offline-first apps with spaced repetition, so the lesson keeps working when the signal does not.
D / Teacher analytics
Dashboards that answer the question a teacher actually has on Monday morning — who is falling behind, and on what — instead of forty charts nobody opens.
03 / Smart board applications
Most interactive boards end up as very expensive projector screens. The hardware is fine; the software on it was never designed for a teacher standing sideways, a child reaching up, or a lesson that has to switch from writing to a poll to a video in ten seconds. We build smart board applications for exactly that — and this one works. Try it.
Ink that feels like chalk: pressure-smoothed strokes, a highlighter that does not bury the text under it, and an eraser that only takes what you touch. Go on — draw on it.
Pardus ETAP, Android and Windows builds from a single codebase, tuned for the hardware already on the classroom wall.
Lessons are cached on the board itself. When the school network drops, the lesson does not.
Ink over slides, video, web pages and PDFs, and keep every annotation with the lesson it was written on.
Every board session saved as a PDF and sent to students' devices, so nobody copies the board down at the bell.
Push a page to every tablet, pause the room, collect answers — from the board, without walking to a laptop.
Controls placed at a height a child or a wheelchair user can reach, high-contrast themes and type that stays legible from the back row.
04 / Mobile apps for education
The board holds forty minutes. The phone holds the rest of the day — revision on the bus, a grade in a parent's notifications, a register taken before the bell. We build the three apps a school actually needs, native on iOS and Android, sharing one backend with the board and the platform.
iOS · Android · Tablet
Lessons, flashcards and homework download ahead of time; everything syncs when the signal comes back.
Quiet hours for students, a daily digest for parents. Nothing from school pings at midnight.
Revision scheduled around what each student is about to forget, not a fixed list for the whole class.
KVKK and GDPR consent flows, parental controls, no advertising and no third-party tracking.
05 / Approach
Education software fails in the gap between the people who buy it and the people who use it. We close that gap the slow way: by being in the classroom, and staying there until the thing works.
01 — Week 1–2 · In school
Before a single screen is drawn we watch real lessons — where the teacher stands, what gets written twice, the minute lost every time the projector wakes up. The brief is what the room tells us, not what the tender says.
02 — Week 3–6 · Studio + classroom
Not on a laptop, and not in Figma alone. Prototypes run on the boards and tablets the school already owns, at the height a nine-year-old can reach, with the glare from the window side of the room.
03 — Week 7–12 · Pilot
One teacher, one class, one term's unit. We sit in again, measure what changed, and fix what the pilot found before a second classroom ever sees it.
04 — Term 2 onward · Rollout
Staged across the school, with short training sessions teachers can actually attend and a handful of in-house champions who answer the questions we would otherwise be phoned about.
06 / Standards
Children are not ordinary users, and schools are not ordinary customers. These hold on every education project we take, whatever the budget.
KVKK and GDPR compliant by design. Minimal collection, hosting in the region you require, and nothing sold, profiled or shared with advertisers. Ever.
WCAG 2.2 AA as the floor, not the goal: screen readers, keyboard, captions, dyslexia-friendly type and colour that works for colour-blind students.
Light pages, offline modes and sync that waits patiently. Designed on a throttled connection, because that is the one most classrooms have.
Open formats, full export and no lock-in. The lessons a teacher builds are theirs to take with them — including away from us.
Tell us about the classroom — the age group, the hardware on the wall and what keeps going wrong. We will come back with what we would build first.