interactive concept learning application. ask a question and ponder pairs a clear explanation with an interactive model.
- streaming explanations generated by gemini
- serper.dev web search for grounded answers and citations
- sourced images via wikipedia and serper image search
- interactive visualisations: graphs, simulations, step explorers, timelines, comparisons, diagrams, calculators
- conversation history, saved explorations, private notes
- shareable read-only exploration snapshots
- google sign-in and firestore persistence
- automatic transfer of your temporary workspace (chats, saved explorations, notes) and API credentials into your account when you sign in
- mandatory gemini and serper api key onboarding
- pdf export and text-to-speech listening
- react 19, typescript, tailwind css 4, vite
- express server with server-sent events
- google gemini api
- serper.dev api
- firebase authentication and cloud firestore
- node.js 20 or newer
- npm
- a gemini api key
- a serper.dev api key
- a firebase project (optional, for auth and persistence)
npm install
cp .env.example .env
# edit .env and set GEMINI_API_KEY and SERPER_API_KEYnpm run devthe application runs at http://localhost:3000.
see .env.example. GEMINI_API_KEY is required for explanations. SERPER_API_KEY is required for web search. firebase client configuration is read from the VITE_FIREBASE_* variables (see .env.example). Server-side account credential storage additionally requires FIREBASE_SERVICE_ACCOUNT_JSON (or GOOGLE_APPLICATION_CREDENTIALS) and a stable PONDER_ENCRYPTION_KEY.
you can use ponder without signing in. in that case your chats, saved explorations, notes and api keys live only on this device / in a browser session.
when you sign in with google for the first time on that browser, ponder automatically:
- moves your temporary chats, saved explorations and notes into your account's firestore data (ids are remapped so everything still links up)
- copies the gemini and serper api keys you entered into your account's encrypted credential store (an existing account key is never overwritten)
- clears the temporary local data once the transfer succeeds
this runs once per account per browser. after that, everything is stored under your signed-in account.
npm run test
npm run typechecknpm run build
npm run startbuild the frontend with npm run build, then run npm run start with NODE_ENV=production. the express server serves the built assets and api routes.
firebase rules are in firestore.rules.
