惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News | PayPal Newsroom
P
Proofpoint News Feed
Cyberwarzone
Cyberwarzone
C
Cisco Blogs
SecWiki News
SecWiki News
Know Your Adversary
Know Your Adversary
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Vercel News
Vercel News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
罗磊的独立博客
NISL@THU
NISL@THU
WordPress大学
WordPress大学
Hacker News - Newest:
Hacker News - Newest: "LLM"
T
Threat Research - Cisco Blogs
AI
AI
Simon Willison's Weblog
Simon Willison's Weblog
Security Archives - TechRepublic
Security Archives - TechRepublic
有赞技术团队
有赞技术团队
L
LINUX DO - 热门话题
Hacker News: Ask HN
Hacker News: Ask HN
V
V2EX
G
GRAHAM CLULEY
TaoSecurity Blog
TaoSecurity Blog
Hugging Face - Blog
Hugging Face - Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
F
Fortinet All Blogs
博客园 - 叶小钗
博客园 - 三生石上(FineUI控件)
云风的 BLOG
云风的 BLOG
Recorded Future
Recorded Future
Latest news
Latest news
The Hacker News
The Hacker News
aimingoo的专栏
aimingoo的专栏
T
Troy Hunt's Blog
S
Schneier on Security
I
Intezer
Google DeepMind News
Google DeepMind News
A
Arctic Wolf
Apple Machine Learning Research
Apple Machine Learning Research
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
T
Threatpost
爱范儿
爱范儿
The Register - Security
The Register - Security
S
SegmentFault 最新的问题
Blog — PlanetScale
Blog — PlanetScale
博客园 - 聂微东
宝玉的分享
宝玉的分享
Recent Commits to openclaw:main
Recent Commits to openclaw:main
美团技术团队
B
Blog RSS Feed

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
6 years building Planning Poker Online: from a weekend project to 147K users (and 3 mistakes I had to fix)
Miquel Las H · 2026-05-11 · via DEV Community

In early 2020 I built a real-time planning poker app over a weekend, almost by accident. Six years later, 147,000+ people use it every month, including teams at Google.

This is a story about Firebase, Hacker News, a €60k mistake, and what I'd do differently if I started today. Especially relevant if you're building a SaaS in 2026 and worried about LLM-era discovery.

The 2020 origin

In 2019 I was working as a frontend developer in a distributed team. At the start of every sprint we would always do the same estimation meeting: how many difficulty points each task should have, how to split them, etc. The "sprint planning meeting".

To not influence others, each team member has to say their estimation secretly, and on the count of 3 we all show our estimations and discuss the results. But… how do you do that in a video call?

Those sessions felt quite unprofessional and boring. To cast the votes we all wrote our estimations in the meeting chat at the same time. I am sure some team members cheated and waited until they saw other estimations to cast theirs xd. In a previous company we were using fingers in the camera — imagine trying to see all the fingers of a whole team and count estimation points xD.

Back in 2019, Google Firebase was becoming very popular. I was especially interested in the real-time capabilities — they had just launched Firestore and I wanted to give it a try. I thought it would be fun to build a small tool for my team so we could do proper estimations.

After shipping the first version of the planning poker app (early 2020), I was a bit shy or concerned about presenting it to my team and company, so I decided not to. Instead I posted it on Hacker News, Product Hunt, LinkedIn, etc. To my surprise the post on Hacker News gained big traction, and in 1 week I had 2,000 users!

Early decisions

A few early decisions shaped everything that followed:

Choosing the domain for SEO

While many companies pick their brand name for the domain, I decided to pick a domain name in SEO terms. I saw that "online planning poker" or "planning poker online" were highly used to find tools like mine, and planningpokeronline.com was available, so I went for it.

This had a great benefit in the early days: very quickly we ranked #1 in search results, which brought us a lot of traffic. But for the long term, it has been a problem, as we don't have a strong brand name for our app.

This has been even more painful now in AI times. LLMs are good at identifying tokens: when they find a brand name they know it is a brand and they store every occurrence in their models. We are usually mentioned as "planning poker online", which is often not related to our brand but to the technique itself.

Posting on Hacker News, 2k users in a few days

Posting on Hacker News got big attention. In just 2 weeks we went from a freshly shipped prototype with 0 users to 2k users.

Those users gave me really good feedback directly. Having a dedicated tool to run those meetings made teams feel more engaged and professional, and they were having fun. That's when I realized I was onto something.

Onboarding the designer, the professional touch

The app was useful, but you could tell it was a prototype made by an indie developer.

When Oriol, our designer, joined the project, the app became a real professional app. I remember looking at the site and thinking, OMG this is a real app. It wasn't the first app I'd launched publicly, but this one felt really mine, as I had started everything from scratch.

This is how our landing page looked in the early 20s:

weagileyou.com landing page in 2020
Our landing page in the early 2020s.

Simple & Fun: The Real-Time Poker Table

This has been the key decision point in our success: while other apps felt like filling boring spreadsheets, we made a tool that felt like a real game.

You can see when a player joins a room because their avatar appears next to the table. When they cast their vote you see their cards turning blue, and when showing the cards, a nice flipping animation comes in revealing the results of the voting round.

We even made it possible to throw stuff at other players around the table, like you would shoot Nerf darts in an office. You can throw whatever emoji you want, or predefined objects like Nerf darts, paper balls, or paper planes.

This is a screen of our landing page from 2022 where you can see how our table looked back then — it hasn't changed very much:

weagileyou.com landing page in 2022, showing the real-time planning poker table
Our landing page in 2022, the real-time poker table design we still use.

The no-signup decision

Making the app simple has been a top priority for us.

Create a game in 2 clicks: trying our app with the team just needs 2 clicks. The first one brings you to the create game form, the second submits the form with default configs and redirects to the game ready to play.

Developers just join and play: when they click the game link shared by the facilitator, they just see one small popup asking for a display name, and they can start estimating issues right away.

Making it easier for the facilitator has been key, but making it easy for developers has been even more important. We tried very hard to stay out of their way and let them just run their estimation meetings with ease.

This has some downsides, obviously. For example, it makes remarketing harder: as we don't collect email addresses we can't contact our churned or inactive users. But I think it has been a good decision so far.

6 years timeline

As the app became more popular, some people in my company saw on my LinkedIn that I was sharing stuff about my Planning Poker app, and they wanted to try it.

This became crucial to fine-tune the app: I was a real user of the app in every sprint. In every meeting I could see something to improve and write it down in a note.

The app started to grow massively. By April 2020 we released the premium plans. I still remember the first customer — it was amazing seeing someone willing to pay for something I built. This was the "proof of concept": we had not only a good tool but also a potential business.

The business kept growing really organically for years.

Listening to our users: The Jira Plugin

Some users asked if the app could integrate better with their Jira. So we decided to build a dedicated version of the app for Jira.

Having our app running inside Jira has great benefits for companies:

  • The Planning Poker table runs directly inside Jira, so there is no need to switch to another app.
  • Estimations sync seamlessly with Jira issues.
  • They don't need to set up a new vendor in their company, which usually means dealing with new data providers, new user accounts, an approval process, and so on.

We released the plugin in March 2024, and many of our web users switched to it. It was a big success. They were giving us great feedback, so it became a priority to make it the best planning poker app on the Atlassian Marketplace.

Planning Poker Online running natively inside Jira
The Jira plugin today: the poker table running inside Jira.

The Retrospectives app

In February of this year (2026) we launched the final version of our Retrospectives app; both the web app and Jira plugin versions launched together. Our customers are loving it; the feedback has been really good.

A retrospective is an Agile ritual that runs after each sprint, where the team analyzes what went well and what didn't, and defines actions to improve their performance.

Our retros app follows the same principles: it feels like a game, and it is simple and fun. You can also throw stuff at teammates here! xD

We are actively working on improving this app. Don't hesitate to send feedback!

What we changed our minds about

The "big tool"

After the success of the Planning Poker app we thought we could create a full project management tool (something like our own Jira for Agile companies). We changed our minds and decided to make standalone apps for Planning Poker and Retrospectives. Here's why:

  • Each app keeps the maximum simplicity. Just one button to create the planning poker or retro and done.
  • Teams can plug and play apps easily. They can purchase the app they need for the time they need it.
  • Companies can keep using their existing project management tools: Jira, Asana, Linear, Trello, Todoist, etc.
  • It makes it easier for us to improve and simplify each app.

Paid Media

When I talked to other founders, many of them advised me: "Now that you have a working business model you need to invest money in scaling up", so that's what I did. I spent more than €60k in just one year on Google Ads only to see it didn't work. "Keep waiting, it will improve," I was told. You know what? Deleted money.

I realised that, at least for our case, we need to appear on the screens of our potential customers in the moment they are searching for the tool. So SEO was our best organic channel. Which brings me to the third thing we had to change.

Relying only on SEO

Our SEO was so good (we are the first result for "planning poker" in many search engines) that we thought it was the only thing we needed. And this worked well for many years, but now in AI times it has been a disadvantage.

To people starting now I would recommend picking the brand name for the domain and making sure LLMs know about your brand and recommend it. Although nowadays there are so many things changing that who knows which would be the best choice in the future :)

What we got right and stuck with

"Our app has to feel like a game, not like filling bureaucratic forms"

This has been a key differentiation point for us, and it has been our best feedback since day 1.

In our feedback tool, users report things like:

"team loves it and promotes conversations"
"Stays out of the way in a really nice way. Only does its job. Great work!"
"Easy to understand :) nice little robot <3"
"Feels really simple to use and can be overviewed quite nicely"

And the most loved feature, by far, is throwing stuff at colleagues xD:

"Throwing emotes to colleagues"
"I like throwing things at people"
"throwing the emojis to people is hilarious"
"it's super easy to use, team really likes the ability to 'throw' things at each other"

The Planning Poker Online real-time table in 2026
Our poker table today, same philosophy as day 1.

Closing reflection

I always loved coding and crafting the best stuff I could for others to use. Seeing more than 147,000 people using the apps we built feels amazing and keeps me wanting to improve them every day. (Don't worry, we won't start adding features without any sense xd.)

I am always happy to talk, so feel free to reach me on LinkedIn or try our apps: Planning Poker Online and Retrospective Online.