Choosing what to build. The marketplace already has a long tail of templates. Building something that doesn't overlap with existing listings — but also solves a real need — requires actual selection discipline. Not every gap is worth filling.
Building to FlutterFlow's submission pipeline. Every template has to ship with instructions, reference docs, marketplace images, iOS screenshots, a cover image, a thumbnail, and widget code that works within FlutterFlow's cloud build. Pub package constraints are real — some packages that work in plain Flutter break inside FlutterFlow's build system.
Full-app templates versus widget bundles. Some buyers want a single widget they can drop into an existing project (a chart, a QR code generator, a story view). Other buyers want a complete starting template (a real estate app, a scheduling app). These are different products and need different architectures.
Building credibility on a marketplace without reviews. New templates have no social proof. A first sale is much harder to win than a tenth sale.
Thematic coherence on the second batch. After the first three templates hit the marketplace, it became clear that buyers don't shop one widget at a time — they tend to need a small cluster at once. "I need a chart and also a chip input" happens together. "I need a rich text editor and also markdown rendering" happens together. The second batch had to be designed around that pattern.