Profile 01 · The Founder

Built from
zero
to live

I started DormDrop with no technical background — no prior web development, no existing codebase, no team. What existed was a problem worth solving and the discipline to learn everything required to solve it. The product is now live at two Charles University dormitories.

Live at dormdrop.cz
DormDrop
Peer-to-peer circular marketplace · Charles University
Live · 2025–26
2
Pilot dorms
PWA
Platform type
Solo
Founding team
Vanilla JS HTML / CSS Supabase WEDOS PostHog Resend
01

The founding
story

01
The observation

Every semester at Charles University dormitories, usable items are thrown away as students move out — while incoming students spend money on the same items. The exchange already happens informally. No tool supports it at the dorm level.

02
The decision

Instead of finding an existing platform, I decided to build one. With no prior web development experience, I began learning HTML, CSS, and JavaScript from scratch — using the product itself as the learning environment.

03
The reframe

Early on I recognised that a marketplace was the wrong model. The real constraints were speed, proximity, and trust — not price. I redesigned the system as a connection facilitator, removing payments, escrow, and ratings entirely.

04
The launch

DormDrop went live at Kolej Větrník and Kolej Hvězda — two Charles University dormitories in Prague. A pilot MOU was produced, dormitory authority meetings were held, and real listings from real students are now on the platform.

"The best UX solution is often removing complexity, not adding features — especially when designing within real-world constraints."

02

Current
sprint status

Sprint 1 — Platform foundations
In progress · Mar 2026
Done
PostHog analytics live
Cookie consent banner
CU email validation on signup
Rewards page nav fix
Email obfuscation fix
Resend domain verification
RLS across 6 tables
Admin survey results modal
In progress
PWA install prompt
Admin moderation upgrade
Backlog
Push notifications
User profiles
GMV dashboard
Mark-as-sold flow
Privacy policy update
Critical path
First completed transaction
50+ student signups
Investor landing page
May move-out campaign
Most important gap before investor pitches: zero completed transactions. Listings exist. The exchange loop needs to close.
03

Technical
architecture

Frontend
Vanilla stack
HTML / CSS / JavaScript
Progressive Web App
WEDOS shared hosting
WebFTP deploy pattern
Backend
Supabase
PostgreSQL database
Row level security (RLS)
Auth with email validation
Storage for listing photos
Services
Third-party layer
PostHog — analytics
Resend — transactional email
DKIM / SPF / MX configured
dormdrop.cz domain
No payments — by design
Removing transaction infrastructure was a deliberate product decision. It reduced legal friction, simplified the UX, and aligned with how students actually exchange items.
University email as trust layer
CU email validation on signup means dorm affiliation is verified at the door. No ratings, no profiles, no reputation system required — the institution does the trust work.
Vanilla JS — a deliberate choice
No framework overhead. Fast to load, easy to debug, fully understood by the sole developer. The constraint of learning while building meant simplicity was also pragmatism.
RLS across all tables
Row-level security enabled across listings, profiles, survey responses, and admin tables. Security as a first-class concern from Sprint 1, not a retrofit.
04

Next concept:
Streaking

Concept · 2025
Campus social
infrastructure

A standalone campus social app separate from DormDrop. Built around shared activity streaks, an interest-and-behaviour graph, and session-based community formation. The hypothesis: students don't need another social network — they need a system that rewards showing up together.

InCircles social graph
Outer / InCircle / Inner InCircle — earned through shared activity, not follows or likes.
Three session types at launch
Study · Pulse · Live Announce — scoped, low-friction, campus-local.
Streak mechanic
Consistency rewarded. Relationships deepened through repeated shared presence.
Status
Concept stage

Architecture defined. Product brief and 12-slide pitch deck outline produced. Not yet in active development — DormDrop takes priority through the May move-out campaign.

Shared DNA with DormDrop

Both products are built on the same insight: the most valuable social infrastructure for students is hyperlocal and behaviour-driven, not network-scale and content-driven.

05

How I
build

01
Start with the problem, not the solution
DormDrop began as an observation, not a product idea. The marketplace framing came second — and was then discarded when research showed it was the wrong model. The problem always comes first.
02
Learn by shipping, not by studying
Every technical skill acquired during DormDrop came from needing it for the product — not from courses or preparation. The build is the curriculum.
03
Remove before adding
Payments, escrow, ratings, dispute handling — all removed. Each removal simplified the UX, reduced legal surface area, and increased adoption. Subtraction is product strategy.
04
Constraints are design inputs, not obstacles
No budget, no team, no prior experience, institutional approval required — every constraint shaped a better product. The dorm-level scope emerged from the constraint of needing dormitory authority approval.
05
The flywheel is traction, not features
The most important metric for DormDrop right now is not code quality, not design polish, not analytics coverage — it is the first completed transaction between two students. That closes the loop.

Interested in DormDrop?

Open to conversations with university administrators, impact investors, circular economy advocates, and potential partners. The May move-out season is the critical window.

Visit dormdrop.cz Get in touch