OptionsLab started with a frustration that most retail options traders know well. The places where people actually talk about trades are signal groups and group chats: someone posts a ticker and a strike, everyone piles in, and nobody explains why. You can follow those for a year and come out no better at trading than when you started. We wanted a place where traders could share real ideas and actually get better, and we wanted it to feel native to the phone, because that is where the conversation already happens.
Start with the conversation
The design process began with a question: what does a trader want from a community on their phone? Not a terminal, and not a chart app. We spent the first two weeks sitting in existing groups, reading how people posted, and noticing where the good threads died. The patterns were clear. People wanted to debate setups, see how a trade was reasoned through from entry to exit, and learn the fundamentals without feeling talked down to. That gave us the three pillars of v1: a community feed with posts and polls, TradeLab for curated trade breakdowns with the why behind every move, and LearnCenter for guided lessons.
Make learning feel like progress
The hardest part was not the feed. It was making the educational side something people came back to. Courses on their own get abandoned, so we built a trade journal to connect what you learn to what you actually do, and layered an XP system on top: finish a lesson, log a trade, contribute to a thread, and you level up. It sounds like a game mechanic, and it is, but it turned LearnCenter from a library into a path. We went through dozens of iterations of the feed and the breakdown view, testing how a setup read on a small screen and how many comments felt like a discussion rather than noise.
Ship, then keep listening
Our design-engineering loop is unusually tight because the same people who design the interfaces also write the code. That means a prototype on Tuesday can be a working build by Thursday. We shipped OptionsLab to the App Store eleven weeks after writing the first line of code. It was not perfect — no v1 ever is — but early users immediately understood what made it different: it is educational first, and nothing in it pretends to be financial advice. We have been iterating ever since, and every update still ships from the same tight loop that built the original.
Keep reading
More from the studio
Two products, one studio: how we split our time
Running ExpertNest and OptionsLab in parallel with a small team — what works, what hurts, and the rules we made for ourselves.
Why We Build Everything In-House
The case for owning your entire product stack — and why it makes us move faster, not slower.