Arktur – explore architecture and building history around you (iOS)
Polished iOS app for architecture tours, but similar city guide apps already exist.

A/B testing tool that forces hypothesis tracking to build a searchable insight history.
Indie founders, Product managers, Small startup teams
Optimizely · PostHog · VWO
This is the core problem with A/B testing for small teams. Each experiment gets evaluated on its own. The result gets shipped or discarded. The reasoning disappears. But insights compound across experiments. "Outcome-focused copy outperforms feature lists for cold traffic" is not something you learn from one test. You see it after five.
Blazeway runs the experiment and captures the reasoning in the same flow. Before a test starts, a short wizard walks you through what you observed, what you think is causing it, what you have planned to change and what counts as a win. While it runs, you see live visitor counts and statistical significance. When it ends, you write one sentence: what you learned.
No enterprise setup, no $200/mo plan. Five minutes to first experiment.
Do that ten times and you have a searchable record of why your product looks the way it does. One click hands your entire experiment history to the LLM of your choice, packaged with a pre-written prompt that already asks the right questions. Because every experiment is grounded in your own observations and hypotheses, the LLM reasons about your product, your users, and your specific assumptions. It can tell you why things worked, why they didn't, and what that means for what you should test next.
Cookieless, GDPR-compliant. Pro is free during beta. https://blazeway.app
Polished iOS app for architecture tours, but similar city guide apps already exist.
This isn't another Firebase clone — it bakes authorization into the data model (you specify access when you create facts) and uses an RDF-style facts/triples API plus CRDT/OT for real-time merges. The demo hooks (useKeyValueAttributes) and OpenID Connect support make the client story feel thought-through, so this is worth a look if you need server‑sovereign, multi-app data sharing rather than a client-first offline story.
Forces teams to document NOLINT suppressions before tech debt accumulates.
Headless docs separation when Quartz and Obsidian bundle everything together.
Prompts AI to fix a11y during generation, not after; early-stage experiment.
Permissionless enforcement + charity splits make cheating expensive, but it's a blog post about one person's experiment.