bjcp-app

The description states that bjcp-app is a gamified web and native app for studying the BJCP 2021 beer judge certification exam. The app presents 125 beer styles through bite-size quizzes, streaks, XP, and a virtual cabinet metaphor where mastered styles appear as colored bottles on shelves. It is built as a progressive web app (PWA) and a native iOS/macOS application with cloud-synced progress.

The author claims to have built the entire system solo, using a content pipeline from DOCX to JSON, shared logic between web and iOS clients, local-first storage with sync to Supabase, and a pixel-art bottle reveal animation. The app uses adaptive quiz engines targeting 80–90% accuracy and includes features like spaced repetition.

This analysis is based entirely on self-reported information from the project description, with no independent verification. The author’s account does not include any data about users, customers, monetization, traction, or commercial activity.

The description states that bjcp-app is a gamified study tool for the BJCP (Beer Judge Certification Program) 2021 exam. It presents 125 beer styles through interactive quizzes and visual metaphors, such as a virtual cabinet where mastered styles appear as colored bottles.

It includes:

• A tech-tree progression system across families → sub-families → styles.
• Multiple quiz formats: multiple choice, SRM matching, style duels, off-flavor ID, flavor wheel, map quizzes.
• XP, levels, streaks, badges, and hop shards for engagement.
• Cloud-synced progress between a PWA and native iOS/macOS app.
• A content pipeline parsing DOCX files into JSON models.
• Local-first storage with sync to Supabase (PostgreSQL + auth).
• Pixel-art bottle animations triggered upon mastering styles.

It is described as being built using:

• Web: Next.js, React, Tailwind CSS, Dexie.js, IndexedDB, Playwright, Vitest, PostHog
• iOS/macOS: SwiftUI, SwiftData, Swift
• Backend: Supabase (PostgreSQL), Python-docx, Python

Inference The app appears to be a single-developer project focused on education and gamification, with no evidence of commercial traction or user base.

The description states that the app is designed to make studying for the BJCP exam feel like collecting beer styles — turning a dry academic task into an engaging experience. It positions itself as a replacement for traditional tools like PDFs and flashcards.

It claims:

• The app turns 100+ pages of guidelines into an interactive game.
• Users can "fill a virtual cabinet bottle by bottle."
• Progression is gamified with XP, streaks, badges, and levels.
• It supports both offline (PWA) and online (iOS/macOS) modes.

Inference The positioning reflects a niche educational product aimed at amateur beer judges or enthusiasts. There is no evidence of broader market positioning or branding beyond the author’s personal use case.

The description states that bjcp-app targets individuals preparing for the BJCP (Beer Judge Certification Program) exam, which involves memorizing 125 beer styles with detailed characteristics.

It implies:

• The primary user is someone studying for a certification.
• The app is designed for people who find traditional study methods unengaging or overwhelming.
• It appeals to hobbyists and professionals in the brewing industry.

Inference The target customer appears to be a small, niche group — likely amateur beer judges or those training for certification. No evidence of segmentation beyond this core use case.

The description does not state anything about pricing, monetization, or business model.

It mentions:

• A "free vs. premium tiers" concept in the tech-tree design.
• No explicit mention of paid features, subscriptions, or revenue streams.

Inference There is no evidence of a monetized business model beyond the author’s own development effort.

The description states that bjcp-app was built with:

• Web stack: Next.js, React, Tailwind CSS, Dexie.js, IndexedDB, Playwright, Vitest, PostHog
• iOS/macOS stack: SwiftUI, SwiftData, Swift
• Backend: Supabase (PostgreSQL + auth), Python-docx, Python
• Deployment: Vercel PWA

It also mentions:

• A content pipeline parsing DOCX into JSON.
• Shared logic between web and iOS clients.
• Local-first storage with sync to a merge layer on Supabase.
• Pixel-art bottle animations using image compositing.

Inference The technical stack is modern and well-structured for a solo developer. It shows attention to cross-platform parity, offline support, and user experience design.

The description does not provide any evidence of:

• Users or customer base
• Revenue or monetization
• Adoption metrics
• Product usage data
• Growth trends

It states that the app was built by one person (경태 이) and submitted to a hackathon.

Inference There is no evidence of traction, maturity, or commercial viability beyond the author’s own development.

The description does not mention any competitors or market context.

It implies:

• The app fills a gap in traditional BJCP study tools (PDFs, flashcards).
• It introduces gamification to an otherwise dry subject.

Inference No evidence of competitive landscape or prior products in this space is provided.

The description does not state any risks or red flags directly. However, based on the self-reported nature and lack of traction:

• No revenue or user base: The app has no demonstrated commercial viability.
• Single-person development: No team or external support implies limited scalability.
• Niche market: BJCP exam prep is a very small segment; growth potential may be limited.
• Unverified claims: All features and functionality are self-reported without independent validation.

Inference The lack of evidence for adoption, revenue, or even basic user feedback suggests high risk in terms of commercial viability and scalability.

1. What is the actual size of the BJCP exam prep market? Is there demand beyond your own use case?
2. Have you tested the app with other users, or is it purely personal development?
3. How do you plan to monetize this product if at all?
4. Are there any plans for expanding content beyond the 2021 guidelines?
5. What are the technical challenges in scaling sync and offline capabilities across more users?
6. Do you have any feedback from potential users or testers?
7. Is there a long-term roadmap for features, localization, or community building?