How I Built PATH SSC — A Government Exam Companion (Honest Build Journal)

Every day, lakhs of students in India prepare for government exams — SSC GD, CHSL, CGL, MTS, and Railway NTPC / Group D. They search for syllabus, practice questions, mock tests, and notes. I wanted to build something genuinely useful for them. Not another flashy app with fake reviews, but a clean, honest study companion.

This is the build journal of PATH SSC — what it is, what is real today, what is not, and the honest choices I made along the way.

The problem I wanted to solve

Government exam aspirants juggle a lot of moving parts:

• Syllabus coverage across Mathematics, Reasoning, English, and General Awareness.
• Practice — lots of it — with questions that reflect the real exam pattern.
• Mock tests that teach you time management.
• Notes organized by subject and topic.
• Progress tracking — knowing where you stand and what to revise.

Most platforms try to do all of this at once, but they layer on noise: fake leaderboards, inflated student counts, "live" competition that is actually canned data. For a student, that noise is worse than useless — it misleads you about your actual readiness.

So when I started PATH SSC, I set three rules for myself:

1. Advertise only what is real. If a feature does not work yet, I will not claim it does.
2. No fake statistics. No invented success rates, rankings, or user counts.
3. Build the foundation first. A clean, organized structure beats a hollow facade.

What PATH SSC is today

PATH SSC is a React 18 + Vite 5 frontend application with:

• 22 screens covering the core student journey: Home, Tests, Jobs, Store, Profile, and pushed detail screens.
• A verified design system — teal #218DAE, cyan #2BBBD7, and yellow #FFD758 — defined in the global stylesheet.
• A PWA manifest so it can be installed as a web app.
• Navigation for Home, Tests, Jobs, Store, and Profile.

Let me be precise about what is verified and live right now:

Verified and real today

• Exam categories — the catalog structures for subjects, topics, exam categories, and notes categories are real metadata, built as seed data.
• Quiz seed content — there are 12 real-style practice questions in the quiz bank. These are genuinely written SSC-style questions, not placeholders.
• UI structure — the screens, navigation, and layout are fully implemented.
• Onboarding gate — uses localStorage to remember whether a user has completed onboarding.

Not live yet (honest disclosure)

• No backend. There is no server, no database, and no authentication. All state is frontend-only.
• No real notifications. The notification panel uses a static sample array.
• No live job data. The Jobs section contains hardcoded sample jobs with invented vacancy numbers — these must NOT be taken as real government openings.
• No live AI. The "AI Teacher" screen exists, but it answers with canned static replies. There is no model connection.
• No real PDFs. The Notes Library has six categories with metadata only — no actual PDF files exist yet.
• No real leaderboard. The leaderboard contains invented users. It is a demo.
• No payments. The Store/Plans show demo pricing with no payment integration.

I say this plainly because it matters. A student who trusts a tool deserves to know exactly what it can do today. PATH SSC is a frontend-only prototype, and I will only ever advertise what has been verified.

The tech stack

The stack is deliberately simple and modern:

• React 18.3.1 — component-based UI.
• Vite 5.3.4 — fast build tooling and dev server.
• lucide-react — clean, consistent icons.
• Plain JavaScript — no TypeScript complexity for this stage (a deliberate choice to keep the prototype fast to iterate).
• State-based navigation — a custom navigation implementation, not a heavy router dependency.

Why this stack? Speed of iteration. For a prototype, I wanted to move fast without fighting tooling. Vite gives instant hot reload, and React keeps the UI organized as screens multiply.

What I learned building it

1. Honesty is a feature

It is tempting to ship a demo with a fake leaderboard and claim "join 10,000 students." But a student who discovers the lie loses trust in the whole product. Early on, I decided that verified features only is a positioning strategy, not a weakness. In a market full of inflated claims, a tool that tells the truth stands out.

2. Structure before content

The hardest part of a study app is not the code — it is the organization of knowledge. Getting the category tree right (subjects → topics → exams → notes → quizzes) is what makes everything else work. I spent real effort on the catalog metadata because that is the skeleton of the product.

3. Seed content must be real

It is easy to fill a quiz bank with garbage placeholder questions. I chose to write 12 genuine, real-style questions instead. Even a small bank of high-quality questions is worth more than a large bank of junk. This also sets the quality bar for future content.

4. Prototypes deserve a plan

A frontend-only prototype is a starting point, not the end. My roadmap is clear:

• Backend: Node.js + Express, with SQLite for data persistence.
• Real authentication: user accounts with real profiles and progress.
• Secure PDF delivery: real study material delivered properly.
• Verified AI routing: when the AI Teacher is powered by a real model, it will be clearly labeled.

5. Constraints are a feature, not a bug

Shipping frontend-only forced me to be honest about scope — and that turned out to be a gift. Because I could not fake a backend, the product's boundaries are exactly its real boundaries. The prototype's design polish and category metadata are genuinely excellent, which gives me a strong foundation to bolt a real backend onto.

6. The audience defines the pace

Government exam aspirants often study on budget Android phones with patchy connectivity. That shapes decisions: the PWA + lightweight frontend means the app feels fast even on modest hardware. An installable web app that opens instantly is more respectful of a student's constraints than a heavyweight platform.

For developers: how the project is organized

If you are building something similar, here are the concrete patterns I used:

• Design tokens in CSS. The color palette lives in src/styles/global.css — one place to change the whole theme.
• Data as modules. Seed data (categories, topics, quiz questions) lives in structured JS modules under src/data/, separate from components. This makes it easy to swap real data in later.
• Component-per-screen. Each major screen is its own component, and navigation is explicit — easier to reason about than magic routing at this scale.
• Manifest and icons. The PWA manifest and icon.svg are in place, so the app is installable even in prototype form.

A realistic feature roadmap

Here is what I plan to build next, in order:

1. Node.js + Express backend with a REST API.
2. SQLite database for users, progress, and bookmarks.
3. Real authentication (email/OTP) with secure sessions.
4. Real notes library with secure PDF delivery.
5. Expanded question bank — hundreds of genuine SSC-style questions.
6. Verified job feed integration — only official, verifiable government notifications.
7. Real AI Teacher powered by an actual model, clearly disclosed.

Each of these will be shipped and advertised only when it is genuinely working.

Why I am publishing this

I am publishing this build journal for two reasons:

1. For students: so you know exactly what PATH SSC can and cannot do today — and so you can trust that when a feature is announced, it is real.
2. For developers: so you can see an honest, frontend-first build process with a clear path to a full product.

EdTech is full of hype. I want PATH SSC to be the exception — a tool that respects its users enough to tell the truth.

A note on the exam landscape

Let me ground this in the actual exam context, because the product only makes sense against the real world it serves.

• SSC GD (General Duty) — conducts recruitment for Constable posts in the Central Armed Police Forces (CAPF), SSF, and Rifleman roles. The exam has four sections: Mathematics, Reasoning, English, and General Awareness.
• SSC CHSL — higher secondary level, recruits for LDC, DEO, Postal Assistant, and similar posts.
• SSC CGL — graduate level, for Group B and Group C posts across departments.
• SSC MTS — multi-tasking staff, a hugely popular entry-level exam.
• Railway NTPC / Group D — conducted by RRB for thousands of posts each year.

What all of these share is a heavy emphasis on speed and accuracy. Candidates face a fixed time limit, a negative marking scheme, and a cutoff that keeps rising. The difference between selected and not-selected is often a handful of marks — which is exactly why practice quality matters more than volume.

The section-wise reality

• Mathematics rewards technique. Shortcuts, formula sheets, and daily timed drills move the needle more than re-reading theory.
• Reasoning is the most "trainable" section — patterns repeat, and consistent practice builds pattern recognition fast.
• English demands vocabulary and grammar fundamentals plus daily reading.
• General Awareness needs current affairs discipline and static GK revision.

A companion app that respects this structure organizes content the way the exam is actually built: by subject, by topic, by exam. That is exactly the architecture PATH SSC's catalog follows — and it is one of the few things I can point to today as genuinely verified.

How I think about the practice loop

A student's daily routine is simple, but the tools around it are often bloated. The loop that matters is:

1. Study a topic from organized notes/categories.
2. Attempt a timed set of questions on that topic.
3. Review every answer — right ones to lock in the method, wrong ones to find the gap.
4. Bookmark the misses so they become the next day's first task.
5. Repeat with a growing bank of correctly-answered topics.

The product is being built around exactly this loop: subject-wise categories, time-bound attempts, review, and bookmarking. The 12 real-style seed questions prove the pattern; the full bank is the next milestone.

Monetization — the honest version

Almost every competitor charges subscription tolls and hides pricing behind "contact sales." My plan is the opposite:

• Free core practice — categories, quizzes, and basic tracking stay free.
• One fair paid tier — for advanced features like full-length mock tests, detailed analytics, and premium notes when they exist.
• No dark patterns — no surprise renewals, no fake countdown timers, no "only 3 seats left" nonsense.

I also decided there will be no watermark and no forced signup for a single use. If a student wants to try one quiz, they should be able to without creating an account. Signup should feel like an upgrade, not a barrier.

What good looks like — and how I test it

For every feature I build, I ask three questions:

1. Is it real? Does it work with actual input and produce real output?
2. Is it honest? Can I describe it in one sentence without overclaiming?
3. Is it useful? Would a student actually use it daily?

I test the frontend in a real browser, run the build, and verify the UI flows. Screenshots and DOM checks are part of the routine. When a feature cannot pass these checks, it does not get advertised — it gets fixed.

The longer-term vision

Beyond the next milestones, the vision is a complete, trusted companion for the entire government exam journey:

• Adaptive practice that surfaces your weak topics.
• Honest analytics showing your true progress, not inflated metrics.
• A verified job hub that only surfaces official notifications.
• Community study groups built around genuine help, not spam.

None of this exists yet. But every step on the roadmap is chosen to get there without breaking trust.

Conclusion

PATH SSC is at an honest, early stage: a well-structured, verified frontend prototype for government exam aspirants. It has real exam categories, real seed questions, and a clean design — and it does not pretend to have a backend, live jobs, or AI that do not exist yet.

If you are an aspirant, I hope this gives you a clear picture of what is coming. If you are a developer, I hope the build notes help you think about honesty as a product decision.

The journey from prototype to product is a long one. But building it the right way — with verified features, no invented stats, and a transparent roadmap — is the only way I want to build it.

PATH SSC — Your Government Exam Companion. Only verified features are advertised. No fabricated statistics.