About
A small product with a narrow, stubborn idea.
Node Learn began as a simple observation: the scarce thing in learning is not information, and never has been. It is a knowledgeable person paying attention to your specific work.
Almost every learning product answers a different question — how to distribute content more cheaply, how to keep someone in an app longer, how to compress a subject into short videos. Those are real engineering problems. They are not the problem that stops most people from learning something hard.
What stops them is that nobody is going to look at what they made. You can read every article about writing and still not know why your paragraphs do not land. You can finish a programming course and still write code no one else can maintain. The gap closes when someone who knows the subject reads your work and tells you precisely what to change.
So we built the smallest thing that makes that exchange durable: a shared space between one learner and one teacher, holding the goal they agreed on, the tasks it broke into, the work that was submitted and the feedback it received. We call it alearning relation, and it is the only object in the product that really matters.
Everything else follows from refusing to compromise that. No catalogue, because a catalogue sells access rather than attention. No streaks, because we do not want you here out of habit. No verification badges, because we have not verified anyone and would rather say so.
Honest status
What exists today.
Node Learn is an early-access MVP. The core loop runs end to end; several things are visibly unfinished. Here is the real list.
Working now
- Sign up and sign in with email, Google or Notion
- Age band gate and role selection
- Student and teacher profiles
- Teacher search and learning requests
- Learning relations with goals and tasks
- Evidence submission and feedback
- Structured messaging inside a relation
- Explainable progress and proof records
- Data export and account deletion
- Blocking and reporting
Still being built
- Realtime message delivery (currently polled)
- In-app uploads for avatars and evidence attachments
- In-app notifications for requests and feedback
- Offline and stale-data indicators
- Moderation tooling for reports
We would rather list the gaps than let you discover them. If something below matters a lot to you, say so — it moves up the list.
Where it runs
One codebase, three platforms.
iOS & Android
Native apps from a single Expo and React Native codebase, so both platforms get the same features at the same time.
Web
The same application runs in the browser with a desktop layout — no reduced "mobile web" version and no second product to maintain.
Accessibility
WCAG 2.2 AA is the design floor: 44px touch targets, visible focus, screen-reader labels, Dynamic Type and reduced-motion support.
Tell us where we are wrong
The principles on this site are meant to be held to. If you find a place where the product contradicts them, that is a bug worth reporting.