Menu

My Payment Screens Promised Things My Code Didn't Do
📰

My Payment Screens Promised Things My Code Didn't Do

DEV Community: ruby·MarcoBlch·4 days ago
#Lexj6ye5
#devtoruby#devto#dev#premium#copy
Reading 0:00
15s threshold

Originally published on meridianbuild.dev , my build log for OutfitMaker , an AI outfit planner that works from the clothes you already own.

On September 24 I retired the Pro plan at OutfitMaker. One paid plan, Premium, plus a free tier. I changed the checkout, I changed Stripe, and I moved on.

In October I sat down and read every public page and every payment screen as if I were a new visitor. Not the code. The words. What I found was a second version of my product, living in YAML files and ERB templates, that had kept its own rules while the real ones moved.

This post is about that gap, the PRs it took to close it, and why I now treat copy as code that needs tests.

What the pages were saying

A partial list, all from lines I deleted.

The FAQ still sold Pro. In all five languages (English, French, Spanish, German, Portuguese), the plan section listed a Pro tier with "Unlimited AI suggestions", "30 virtual try-ons per month" and "24/7 dedicated support".…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.