Almost everyone wants to have an app these days. But how do you go about finding the right designers, programmers, and marketers to take your app from an idea to millions of downloads in the app store?

  1. Validate your idea. Not all ideas are as great as you my think, and no one wants to call their baby ugly. Validation can be done quickly and cheaply by creating a simple “Pros and Cons” spreadsheet of your competitors, and running online surveys. But you got to do it.
  2. The planning stage is the last time your have total control – You can save a lot of money in development costs if you have drawn the entire app drawn out on paper. I’m not talking about just the main screens; I mean EVERYTHING. Each pop-up message, every menu option. It seems like overkill, but you’re really designing an architectural blueprint here. Designers and engineer have to follow these “wireframes” so they know what to build, and even so that they can give you accurate estimates. You wouldn’t give a build a blueprint for your house with a downstairs bathroom missing, and expect them to just fill in the blanks would you? If you don’t want to do this, expect to pay your developer team to do the wireframes for you, and never use a company who doesn’t offer this step.
  3. Find the right team for you. In any technical endeavor, it’s hard to pick a good team, especially if you are not very technical yourself. You can be techno-babbled to death, or won over by shinny demos. There are a few simple questions you can ask to make sure the team you’re picking is a good one:
    1. Where is the actual development done (in the US? Or is it outsourced to India?)
    2. How does the team manage their source code? You want to hear them say that they use a version control system like GIT (This is like the Track Changes function in Microsoft Word, but for software code).
    3. How is the team going to help you through the planning process? Are they going to build you a functional wireframe you can play with? How about a basic prototype? The more steps they have early on, the more likely you are to succeed.
    4. Ask to touch and play with real life examples of systems the team has worked with.
    5. Find our if they’ve worked on similar products or in similar industries. A little bit of previous experience goes a long way. Find a team who has already made their mistakes on someone else’s dime, so that you don’t have to pay for it.
  4. Understand the process – You don’t have to become a programmer yourself, but spend sometime educating yourself on the technologies and jargon you will encounter. Unlike building a house, you probably have never seen a software project being worked on as you drive down the road. So your frame of reference is very difficult. The process can be extremely opaque as a result. It’s your money; learn a little about how the sausage is made. I’d suggest learning at least a little bit about how databases work, and how source control works – these two topics alone will allow you to have much honest conversations with your developers.
  5. Don’t launch it and leave it – When your app is all done, getting it in the app store can be tricky. Start finding out what you need to do to get into the Apple store early on – this includes reading their terms of use, which isn’t as bad as you think. Make sure you have a business entity set up, and a registered Dunn and Bradstreet number if you’re going to charge money for you app, include ads, or in-app purchases. And finally, learn about how to promote your app in the stores and on the web. You’ve all heard about SEO, but there is such a thing as App Store Optimization as well.
Previous ArticleNext Article
I help companies turn their technical ideas into reality.

CEO @Sourcetoad and @OnDeck

Founder of Thankscrate and Data and Sons

Author of Herding Cats and Coders

Fan of judo, squash, whiskey, aggressive inline, and temperamental British sports cars.

Leave a Reply

Image generation comparison from February 2026

I spend a lot of time generating images these days for presentations. My typical workflow is fairly scientific: I ask Midjourney to produce a relatively cute image of a frog, a toad, a robot, or some other vaguely anthropomorphic creature doing something related to the slide I’m about to present.

Once I get the image, I expand the background by about 90% so the character ends up in the corner of the slide. That gives me a nice, relatively clean area to drop text on top. Sometimes I use Photoshop to do the expansion. Sometimes Midjourney cooperates. ChatGPT is actually pretty good at this too. Nano Banana is… enthusiastic. It tends to try a little too hard right now.

That’s fun and all. But the more interesting comparison isn’t cute amphibians. It’s boring enterprise diagrams.

Recently I had to generate some architecture visuals for an RFP response. Rather than suffer alone, I decided to turn it into a model comparison experiment.

Below is a slightly simplified (but very real-feeling) prompt I used. The company is fictional. The buzzwords are not:

Create a clean, executive-level architecture diagram titled “Closed-Loop Member Intelligence Platform.”

The layout should be 16:9 and structured left to right with a circular optimization loop surrounding the system.

On the left side, show multiple member touchpoints feeding into the platform:
- Website (class browsing, account login)
- Mobile App (workout tracking, push notifications)
- In-Club Kiosks (check-in terminals)
- Wearable Device Integrations (fitness trackers)

Label this section: “Member Interactions Across Digital & Physical Channels.”

All touchpoints should flow into a large central hub labeled:

“Unified Member Profile & Real-Time Event Engine”

Inside the central hub, include:

- Web SDK
- Mobile SDK
- API Gateway
- Event Streaming Layer
- Clickstream Data Capture
- CRM Data Sync
- Identity Resolution Engine

Include a small sub-caption:
“Event-level data unifies anonymous visitors and active members into a single dynamic profile.”

From the central hub, arrows should flow to a right-side activation layer labeled:

“Real-Time Engagement & Orchestration”

Include these outputs:

- Personalized Workout Recommendations
- Dynamic Class Availability Messaging
- Triggered Retention Offers
- Membership Upgrade Campaigns
- A/B Testing & Experimentation Engine

Surround the entire diagram with a circular arrow labeled:

“Continuous Optimization & Revenue Growth”

Along the circular loop, include metrics:

- Engagement
- Conversion
- Retention
- Lifetime Value

Design style should be modern, minimal, and suitable for an enterprise SaaS presentation.
Use neutral tones with one accent color to indicate data flow.
Avoid clutter.
Make the architecture clear and readable for both technical and executive audiences.

Here are the results.

ChatGPT

Clear winner for “looks like a human consultant made this at 11:30 p.m. before a board meeting.” The text was incredibly legible. The layout was balanced. The hierarchy made sense. It genuinely looked like something you’d expect in a mid-market SaaS pitch deck.

I even did a reverse image search on some of the icons. No exact matches. That suggests they were generated rather than assembled from some common icon pack. Which is pretty cool.

Claude

Claude did something interesting. Instead of just giving me a static diagram, it generated a React application that rendered the architecture visually inside its canvas. I should have guessed this is what that nerd would do… in fact I did guess, but whatever.

That has upsides. I can tweak the code. I can modify the layout. I can version control it. That’s appealing to the nerd in me.

But technically it failed the homework assignent. It wasn’t what I asked for. I asked for a diagram image. What I got was a React app that displayed a diagram that I had to screenshot.

That said, I actually liked the aesthetic. It felt a little more “me.” Slightly less textbook. Slightly more product-thinking.

Gemini (Nano Banana)

The undisputed champion of 2026 in image generation, nano banana, was actually my least favorite of all of the designs. I think there’s something really weird about the arrows on the outside ring of this diagram. Why are there two arrows between “Engagement” and “Conversion”? Why are they different sizes? I did actually find a couple of exact matches when searching for some of these icons here, so so there might be some assembly on top of generation going here, but I cannot tell because these icons are so universal that it’s likely that that could just be a coincidence.

Midjourney

Ah, Midjourney. My current favorite for keynote frogs.

Completely and utterly useless for generating readable diagrams.

It’s phenomenal at stylized imagery. I’ve tuned it so much over time that it practically knows my aesthetic preferences better than I do. It’s like it’s been trained specifically to make amphibians that align with my personality.

The Omni feature (object permanence) is genuinely impressive. If you’re telling a visual story and need a character to look consistent across multiple scenes, or you’re creating a children’s book to convince your six-year-old that haircuts are not a violation of human rights, it’s fantastic.

But enterprise architecture diagrams? Nope, sucksville.

Wrapping Up

I was pretty sure that nano banana was going to run away with this one. Everyone I know works in banking or finance or medicine has been telling me how great the model is for generating diagrams and process flows. They’ve been raving about how things that were not possible three months ago are now completely durable with this model. It was a little bit of a surprise to see that my personal favorite was good old-fashioned ChatGPT. I think, for my personal use, I’m probably going to use Claude to generate diagrams because they’re a lot easier for me to tweak once they’ve been generated.

That said, I think this experiment showed that when I do this kind of work in the future, I’m just going to load up the same prompt in three different models and just pick the one I like the most. Some of it’s going to be personal tastes; some of it’s going to be how well the model interpreted the prompt, and some of it’s going to be the state of that particular LLM and its model on that given week.

And I’m going to stick to only using Midjourney for generating cute pictures of toads.