Apticks

Placement aptitude duels. Two players race through the same 5 questions (quant, reasoning, verbal), and the faster, more accurate one gains rating. Modes: challenge a friend with a link, Quick Match against a player near your rating, a Daily Challenge that's the same for everyone, and company practice built from the topics on TCS NQT, Infosys, Accenture and Wipro tests.

• web/: the Next.js app
• supabase/migrations/: tables, row-level security and every game rule, as Postgres functions
• supabase/seed.sql: the question bank, generated by scripts/generate-questions.ts

All game logic runs in the database. Clients only call the functions granted at the bottom of the migrations, so scoring, timing and ratings can't be tampered with from the browser.

Setup

1. Supabase

1. Create a project at supabase.com.
2. In the SQL editor, run each file in supabase/migrations/ in order (0001 → 0011), then run supabase/seed.sql. Every migration after 0001 is safe to run more than once. Then run supabase/record-migrations.sql, so Database → Migrations lists them too (add a line to it for each new migration).
3. Authentication → Sign In / Providers: turn on Allow anonymous sign-ins (every visitor starts as a guest) and keep Email on.
4. Authentication → Emails → SMTP Settings: turn on custom SMTP. Supabase's built-in sender only delivers to your own team's addresses, and the templates can't be edited without custom SMTP. Gmail works for testing: host smtp.gmail.com, port 465, with your Gmail address as the username and sender, and a Google app password as the password.
5. Authentication → Emails → Templates: in both Magic link or OTP and Change Email Address, put {{ .Token }} in the body. Players save their account and sign in with that code, not a link.
6. Authentication → URL Configuration: set the Site URL to where the app runs.

2. Web app

cd web
cp .env.example .env.local   # fill in your project URL and publishable key
npm install
npm run dev                  # http://localhost:3000

3. Check it works

cd web
npm test                 # unit tests for the helpers in src/lib
node scripts/smoke.mjs   # end-to-end game rules, against a test project

The smoke test plays real duels between guest players, then checks scoring, ratings, the daily rules and the anti-cheat rules. It writes real data, so point .env.local at a separate test project (a second free Supabase project works) or a local supabase start. Against a hosted project it refuses to run unless you set SMOKE_ALLOW_REMOTE=1.

4. iPhone app

ios/ holds the native SwiftUI app. It uses the same database functions, so accounts, ratings and challenge links work across the app and the website. Open ios/Apticks.xcodeproj in Xcode and press Run. ios/README.md covers the module layout, tests and universal links.

Accounts

Visitors play as anonymous guests, and their rating is stored in that browser. On the profile page they can save the account with an email. That keeps the same account and rating, so they can sign in on another device. The profile page can also sign out or delete the account. Deleting removes the name, college, email and rating; the player's duels stay in their opponents' history as "Deleted player", so nobody else loses results.

Question bank

node scripts/generate-questions.ts   # rewrites supabase/seed.sql (Node 22.6+)

Quant and most reasoning questions are generated from templates with computed answers. Picture questions are SVG figures. Verbal questions are hand-written. Running the seed again updates existing questions without creating duplicates.

CI

.github/workflows/ci.yml runs lint, typecheck, the unit tests and a production build on every push to main and on every pull request.