1.1 What My Library App is (in one line)

My Library App is a single system that runs a study library: seat + attendance + billing + reminders + student engagement + owner analytics.

1.1.1 The founder’s philosophy (why this is different)

This platform is built on a very specific belief:

• Library management is only ~30% of the product.
• Student productivity + motivation + wellbeing is ~70%.
• If students are happy and consistent, owners naturally grow.

This is also the core “why” explained in the founder story: the app is built from a student’s lived library experience, not only from an owner’s revenue lens. Source: https://mylibraryapp.in/story

1.1.2 The founder story (short version you can quote in pitches)

From the official story page:

• Started from a “thank you” intent and a real-world observation that most libraries still run manually (pen/paper/cash/confusion).
• Built through multiple rewrites (“5th/6th/7th version”), months of iteration, and difficult personal phases.
• Shipped multi-platform (Microsoft Store first as a personal tribute), then fought the Google Play verification/testing process.

Full story: https://mylibraryapp.in/story

1.1.3 What the founder personally invested (for team context)

These numbers are useful in internal culture + “how serious are we?” conversations:

• Google Play Console developer account (one-time)
• Domain + website costs
• Supabase (database) costs
• Microsoft Store publisher account costs

These costs matter because they show commitment and also explain why pricing is not random — it must sustain infra + support.

1.2 The real-world problem (what world looks like without us)

Most private study libraries (reading rooms) run on:

• paper registers (attendance, fees),
• WhatsApp messages manually sent (reminders/receipts),
• guesswork (“is my library full?”, “who hasn’t paid?”, “who is present right now?”),
• no clean data (no trends, no retention view, no growth loop),
• poor student motivation (no progress feedback, no community, no structure).

This creates two pain points at once:

• Owners lose time, money, and control.
• Students lose consistency, motivation, and clarity.

1.3 Who it’s for (personas)

• Student (primary): preparing for exams/jobs (UPSC/SSC/banking/state exams/campus placements), needs a calm place + discipline.
• Owner (primary): runs a paid-seat study library; wants predictable revenue, fewer conflicts, clear control of operations.
• Developer/Admin (internal role): handles platform-level controls: audits, support escalations, subscriptions/trials, impersonation (for troubleshooting), account deletion approvals.

1.4 What makes it different

Think of it as 3 products fused together:

• Operations OS for owners (attendance + billing + expenses + analytics + lockers + support)
• Discipline OS for students (attendance habit + study logs + planner + community + motivation loops)
• Trust layer (clear statuses, approvals, blocks, audit support flow)

1.5 A 60-second pitch (for owners + students)

Owner pitch (simple):

• “You’ll know who is present, who needs to pay, and what your profit looks like—without spreadsheets.”
• “Students get QR attendance, automated reminders, receipts, and structured study tools—so renewals become easier.”

Student pitch (simple):

• “Attendance + study time + planner + community—everything that helps you stay consistent.”
• “Your library becomes smarter: faster check-in, less confusion, better focus.”