BlupoliFollow the real journey: what we are building, why we make decisions, what works, and what we learn along the way.
Documented milestones and decisions, from the early ideas to recent changes.
We share decisions, progress, mistakes and lessons because the process is worth showing, not just the results. We want Blupoli to grow through tested ideas and make it easy to understand why the product changes.
We share difficulties as well as successes.
We explain alternatives, evidence and changes of mind.
We welcome ideas and share the context for discussing them.
Sharing decisions encourages us to evaluate them carefully.
Documented priorities, not progress percentages or release promises.
Generators must produce reliable, reproducible rounds with useful difficulty.
Bring brand, product, navigation and deployment together without breaking existing routes.
Connect development choices with diagrams, verified evidence and published lessons.
Planned directions, subject to change.
No matching posts. Try another word or clear the search.
A week of rebuilding statistics inside and out: Supabase as the single source of truth, hydration without flicker, ten real cognitive categories and a Cards wellbeing panel that no longer fakes progress. A devlog about measuring what matters and refusing to measure what does not.
Read in DevlogA week of rebuilding statistics inside and out: Supabase as the single source of truth, hydration without flicker, ten real cognitive categories and a Cards wellbeing panel that no longer fakes progress. A devlog about measuring what matters and refusing to measure what does not.
Read in DevlogHow Numberlink went from sixteen near-straight boards to 572 MIT puzzles and then to a dynamic generator that certifies unique solutions inside a Web Worker.
Read in DevlogHow we rebuilt Blupoli Cards’ deck to separate rank, index suit and pips, add classic backs, and protect legibility with automated tests.
Read in DevlogHow we added Baker’s Game to Blupoli Cards by reusing the FreeCell family, specializing same-suit building, and protecting the integration with tests and CI.
Read in DevlogHow we reviewed Number Match solvability, separated four sizes from four difficulties, and rotated the same mobile game without changing its topology.
Read in DevlogHow Blupoli Puzzles separated persistence, events and game state with ports, snapshots and versioned contracts without adding Firebase too early.
Read in DevlogHow Blupoli added apps/cards, dist-cards and a third Firebase Hosting target without folding Cards into Puzzles or duplicating the platform.
Read in DevlogHow Blupoli reduced scripts, build phases, and CI by moving repairs into canonical sources, validating without mutation, and removing duplicate GitHub Actions work.
Read in DevlogHow Blupoli Puzzles centralized game completion with a 1.7-second board reveal, category-themed confetti, shared metrics, accessibility, and light/dark theming.
Read in DevlogHow Blupoli Puzzles built 1,080 base achievements and 237 specials on GameResult, declarative rules, engine signals, and irreversible unlocks.
Read in DevlogHow Blupoli Puzzles redefined session start, migrated local statistics without inventing history, and built trustworthy analytics on the GameResult contract.
Read in DevlogA development diary about the recent Blupoli Puzzles leap: new engines, larger boards, structural difficulty, shared results, streaks and stronger CI.
Read in DevlogA technical PolyPivot Devlog covering board partitioning, dual pivots, colour mixing, reversible scrambling, self-tests and Blupoli integration.
Read in DevlogA Blupoli Devlog on the new lobby, progress dashboard and GameResult v2: one local-first result layer for every game and future challenge systems.
Read in DevlogHow we turned the Blupoli home into a product platform with canonical product data, dynamic editorial content, semantic i18n and regression gates.
Read in DevlogDevlog on Blupoli Puzzles
Read in DevlogDevlog on splitting Blupoli publishing into Blog and Devlog, plus the visual system, shared chrome, build, SEO and navigation work behind the change.
Read in DevlogA technical Devlog on unifying identity, navigation, language and theme across blupoli.com and Blupoli Puzzles with shared UI, persistent state and build gates.
Read in DevlogWhat we learned by auditing and rebuilding puzzle engines: generation, uniqueness, meaningful difficulty, persistence, results, accessibility and responsive product quality.
Read in DevlogHow Blupoli uses covers, diagrams and semantic SVGs to explain architecture and puzzle mechanics, with accessibility, localization, responsive design and build-time validation.
Read in DevlogHow Blupoli Puzzles combines a shared onboarding shell, interaction profiles, explicit recipes and a coverage gate to teach different mechanics without fragmenting the product.
Read in DevlogDominosa, Stitches, Slant, Aquarium, Str8ts and Kropki need different models. What Blupoli Puzzles shares is a verification, uniqueness and reproducibility contract.
Read in DevlogHow we use commits, pull requests, tests and deployments as editorial evidence without turning Blupoli
Read in DevlogHow Blupoli Puzzles prepared Italian, Portuguese, French and German as candidate locales with structure, semantic review, routing, SEO and product QA gates before publication.
Read in DevlogHow Blupoli separates identity, logic, routes, UI and editorial content so languages can expand without duplicating product logic, breaking SEO or publishing fake fallbacks.
Read in DevlogHow we turned the Einstein Riddle into a replayable family of problems through relational modeling, clue generation, solving, uniqueness, difficulty and localization.
Read in DevlogWhat changed when Blupoli passed seventy games in September 2026, and why scale turned discovery, shared UI, taxonomy and quality into platform problems.
Read in DevlogHow Blupoli Puzzles separates specialized engines, a shared product layer and a verification process so a diverse puzzle catalogue can grow without fragmenting.
Read in DevlogWhy Blupoli Puzzles paused expansion to audit UX, UI, architecture, performance and content—and how to turn vague product debt into verifiable work.
Read in DevlogWhy Capacitor became our first Android path: reuse the web product, keep one source of truth and reserve native code for concrete device-specific problems.
Read in DevlogHow one familiar Sudoku helped us test hierarchy, controls, onboarding, feedback, themes and responsive behavior before turning those lessons into a shared system.
Read in DevlogHow Blupoli Puzzles separates shell, states, controls and mechanics to make a coherent interface without flattening each puzzle
Read in DevlogWhy a good puzzle generator needs a solver, uniqueness checks, meaningful difficulty metrics, variety, time budgets and the ability to reject valid-but-bad candidates.
Read in DevlogWhat we learned by growing from one puzzle to dozens of experiences: shared architecture, discovery, quality, difficulty and maintainability in Blupoli Puzzles.
Read in DevlogHow we use AI agents at Blupoli for research, implementation and review without confusing output with progress: context, Git, tests and human judgement.
Read in DevlogHow Blupoli Puzzles separates game engines, interface and catalogue—and why that invisible architecture matters to players.
Read in DevlogThe story of how one Sudoku shaped the architecture, catalogue and product identity that became Blupoli Puzzles.
Read in DevlogA week of rebuilding statistics inside and out: Supabase as the single source of truth, hydration without flicker, ten real cognitive categories and a Cards wellbeing panel that no longer fakes progress. A devlog about measuring what matters and refusing to measure what does not.
How Numberlink went from sixteen near-straight boards to 572 MIT puzzles and then to a dynamic generator that certifies unique solutions inside a Web Worker.
How we rebuilt Blupoli Cards’ deck to separate rank, index suit and pips, add classic backs, and protect legibility with automated tests.
How we added Baker’s Game to Blupoli Cards by reusing the FreeCell family, specializing same-suit building, and protecting the integration with tests and CI.
How we reviewed Number Match solvability, separated four sizes from four difficulties, and rotated the same mobile game without changing its topology.
Real decisions and lessons documented as we build Blupoli.
