Overview
Bibliocards started as a niche utility and became a real product with global usage, recurring revenue, and enough technical depth to justify a full platform architecture.
The current version is live and monetized. In parallel, a V2 rebuild is underway with a cleaner split between mobile client, admin surface, and several NestJS services.
Problem
Collectors needed a cleaner way to browse, track, and reference K-pop photocards across a fragmented ecosystem of spreadsheets, fan-made lists, and inconsistent image sources.
The challenge was not only to ship a usable product, but to maintain a growing catalog, media pipeline, and operating model as a solo engineer.
What I Own
- product direction
- frontend and mobile delivery
- backend services
- database design
- deployment and operations
- media storage strategy
- release workflow
Why It Matters
Bibliocards is the strongest proof in the portfolio because it is not a demo project. It is a working system with traction, margin discipline, and real operational constraints.
Current Architecture
The V2 stack is moving toward:
- React Native for the mobile app
- Angular for the internal admin office
- multiple NestJS services for clearer separation of concerns
- Redis and BullMQ for background jobs
- a media footprint large enough to force practical storage decisions
Results
The product validates both the product side and the systems side of my work:
- real users in multiple countries
- recurring revenue with controlled infrastructure costs
- a large indexed catalog
- sustained solo delivery across the full stack