How CookBook grows

The founders tried having AI generate finished screenshot images.

CookBook's first screenshots were made one by one in Photoshop with paragraph-length captions. Current set: one feature per screenshot, large bold caption stating the benefit rather than the feature name (e.g. 'see which campaigns drive installs', not 'analytics dashboard'), big black device frame, zoomed-in UI. The first three screenshots get the most care since most visitors stop there.

Always running App Store product page optimization (PPO) tests on CookBook's screenshots. Small iterations one at a time: a caption change or reordering screenshots. With low traffic, test a single variant (PPO allows up to 3) and let it run a long time (Apple suggests up to 90 days), since results swing day to day. The team competes on whose idea wins. New variants made by duplicating the screenshot project and changing screenshot one.

CookBook runs custom product pages for separate search intents, e.g. importing recipes from Instagram/social media and meal planning; the first screenshot changes to match the intent. Social proof as the first screenshot is another variant idea.

CookBook took raw app screenshots in each of its ~7 languages and used them in the store screenshots alongside translated captions. Guest advises only localizing store screenshots if the app itself is localized, since translated captions over an English app break trust.