Book Accelerator

A guided reading app that combines chapter summaries, practical examples, and quiz-gated progression to improve retention.

Featured
In progress
Learning Web App
StackNext.js, TypeScript, Local-first state
TagsEdTech, Product Design, Web App, Learning UX
EdTechProduct DesignWeb AppLearning UX

Diagram will render here (add caseStudy.diagram)

Problem Statement

Constraints, scale, and what success looks like.

Book Accelerator is designed to make reading active instead of passive. Each chapter is broken into summaries, examples, and quizzes that unlock the next chapter only after passing.

Solution

How the system works end-to-end.

Book Accelerator is designed to make reading active instead of passive. Each chapter is broken into summaries, examples, and quizzes that unlock the next chapter only after passing.

AWS Services Used

Core services and why they are in the design.

Next.jsIncluded
TypeScriptIncluded
Local-first stateIncluded

Architecture Decisions

Tradeoffs and reasoning behind key choices.

Quiz-gated progression

Users must pass chapter quizzes to unlock the next chapter, reinforcing comprehension before progressing.

Local-first data model for UI phase

The current UI phase stores state in localStorage so product behavior is testable end-to-end before backend rollout.

Security Model

IAM, encryption, and exposure controls.

Client state is scoped to browser storage with explicit reset controls

No external content execution in chapter rendering

Prepared backend contract for server-side entitlement and progress enforcement

Reliability Patterns

Retries, DLQs, idempotency, and resilience.

Safe hydration fallbacks when localStorage content is malformed

Locked chapter safeguards prevent invalid navigation

Graceful empty states when onboarding has not been completed

Observability

Logs, metrics, alarms, and tracing.

Consistent state keys for dashboard, book progress, and notes

Structured error banners and empty-state fallbacks across main routes

Deterministic chapter/quiz models for reliable QA coverage

Cost Considerations

Cost drivers and how you keep them under control.

  • Frontend-only UI phase has near-zero runtime cost
  • Backend plan uses serverless primitives to keep ingestion and API costs predictable

Key Takeaways

What you learned and what you would improve next.

  • Integrate published book ingestion and versioning
  • Add server-side progress sync and entitlement enforcement
  • Enable Stripe-backed Pro subscription for extended access

Technologies Used

Quick scan of tools used in this build.

Next.jsTypeScriptLocal-first state