# Developer Products Published articles for Developer Products. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## +14% activated users for AppSignal: designing a new homepage in code DevFeed: [+14% activated users for AppSignal: designing a new homepage in code]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [Application Performance Management (APM)](), [error tracking](), [Tooling](), [Code](), [Figma](), [Artificial Intelligence]() Tags: [agentic-development](), [ai](), [apm](), [case-study](), [code](), [design](), [design-for-devtools](), [developer-marketing](), [developer-products](), [engineering](), [error-tracking](), [figma](), [product-development](), [tooling]() ### AI overview Evil Martians designed and shipped a new AppSignal homepage primarily in code, combining code, Figma, and AI during exploration and prototyping. The selected direction was validated through an A/B test that showed a 14% increase in activated users over the previous site. ### Source excerpt We designed and shipped a fresh AppSignal homepage in code, then validated it in an A/B test with a 14% lift in activated users. ## 2 Martians, greenfield to MVP in 4 weeks: agentic coding on Rails DevFeed: [2 Martians, greenfield to MVP in 4 weeks: agentic coding on Rails]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [agentic-coding](), [Rails](), [coding](), [React](), [Storybook](), [Open Source](), [stripe]() Tags: [agentic](), [agentic-coding](), [ai](), [app](), [authentication](), [building](), [case-study](), [coding](), [designer](), [developer-marketing](), [developer-products](), [google-analytics](), [onboarding](), [open-source](), [payments](), [platform](), [product](), [product-development](), [production](), [prototype](), [rails](), [react](), [skills](), [storybook]() ### AI overview A designer and an engineer describe how they shipped Thicket, a production MVP, in four weeks using agentic coding with Rails, Inertia, React, and Storybook. They discuss their workflow, project-specific skills, user validation, and the resulting open-source practices. ### Source excerpt A designer and an engineer shipped a production MVP in four weeks on Rails + Inertia. In this post, we share our agentic coding stack, the skills we built, and why it clicked. ## Why I love building developer products DevFeed: [Why I love building developer products]() Original publisher: [Read original article]() Author: Map Published: 2019-03-12T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Software](), [coding](), [systems](), [scaling](), [service]() Tags: [developer](), [developer-products](), [opinions](), [philosophies](), [product](), [scaling](), [software](), [systems]() ### AI overview An opinion piece explains why the author enjoys building developer-focused products. It highlights the potential for software and systems to improve life at scale, the challenge of serving skeptical developers, and the author's personal familiarity with developer-product work. ### Source excerpt For much of my career I've been focused on building out developer or data focused products with the customer in some form or fashion being a developer on the other end. I fully realize now that I'm destined to spend the rest of my career in that space, either that or trying my hand at wine making. There are a few things that I personally find rewarding about the space that I've shared with a number of people individually lately and thought I would share more broadly. First, software really is eating the world. Often developers and entrepeurs ask about what they could build that would be a good business. The reality is about anything that has not been modernized to as a service and improved with software could be. We have far less developers in the world than we need to execute on all the ways we could improve products and life. To me what is interesting is the last part of that last sentence. It is not that the market for developers is huge, which I do believe it is. It more that when we automate with systems we can get amazing economies of scale. I know folks that reminisce and talk about how we're more stressed being always connected and such and that in the old days people got out and worked the fields and enjoyed the sun. They also absolutely physically exhausted their bodies in the process. The ability to make life better at scale is an interesting one and often done through systems we develop. The second reason is the challenge and the reward. Developers are notoriously tough critics. If it feels/smells like marketing then they have an allergic reaction, and that is probably because much of it is done poorly. If they experience really positive/great marketing they latch on more than the average person. Most developers are by nature a bit skeptical... for some reason this resonates with me. But, I've found they are the largest/biggest supporters once they're excited about something. Personally I'd rather folks more critical and then have a few diehard fans than a