13
12 Comments

Don't start with the form, start with the finished thing

Often times I have seen indie hackers start building a product in the flow a user takes. Homepage, form, details page.

Start with the opposite. Build the full details page first with dummy data, the thing which is the true essence of your app.

Then go back and build the form. That way you will realize what the actual requirements are.

on June 6, 2022
  1. 2

    To be honest, I don't think that this tip is very effective.
    As has already been noted in the comments, often enough you don't know what the end product should look like.

    For me, at least until now, it was always so that I worked on the things first, of which I already knew roughly how it should look.

    It's more about finishing something than starting to work on something "from behind".

    In the end, it doesn't really matter what you started with, because the goal should be that you finish something first. If you get stuck because of this tip, then it didn't help you.

  2. 1

    Hey,

    I am totally agreed with your argument mate if they start with the form then there is no thrill about the product but if https://halloweensquishmallows.shop/products/jack-the-black-cat-squishmallow start with the finished thing then there are many chances for conversions.

  3. 1

    We often have two ways. One is to put forward hypotheses first and then make adjustments in the process. The unity of knowledge and action is what it means. You can first establish cognition before starting, or you can move first and then improve your cognition. The important thing is that cognition and action are always one. It doesn’t matter who comes first, but to grow in relation to each other

  4. 1

    I started ignoring all coming soon pages and all landing pages that just show the promise of a product or an idea.

    People have to understand: an idea is NOT a product. As a user, even if your app idea shows promise and is of interest to me, it doesn't mean I would use your product. You might trick me into buying the product (as teleshopping does) with fake promises and solutions to my problems.

    Also, people often don't know what they need/want until they actually try that thing, so even for the indie-hacker such a landing page itself does not confirm or disprove the potential of the business idea.

    1. 1

      In other words, I agree with you: the specific details of the business and how it works are a lot more important than the problem/solution it solves. If your goal is only to sell, of course you can promise whatever incredible solutions without having an actual product.

  5. 1

    That's a great tip! I will use it with the product I am building with some friends!

  6. 1

    i dont understand that. could you explain? is that meta or do you actually mean a landingpage that should contain all the details beforehand before trying to onboard people? if so, i could give you opposite examples that work well too.

    1. 1

      I think OP means that developers sometimes start with the form first (since that's the on boarding flow) but as you develop your full product you might realize than you need more data than you originally imagined so you need to go back and edit the on-boarding form over and over again. This is why it is important to start with the app first (with dummy data) then once you have a very clear idea of the fields you NEED then you build the form with the confidence in mind that you are likely not going to have to worry about updating the form as much and thus not wasting as much time.

      1. 2

        Just realized. Jason Fried has written about this far more eloquently: https://basecamp.com/gettingreal/09.2-epicenter-design

        1. 1

          hm interesting! will check that out, thanks for sharing!

        2. 1

          That’s a great article!

      2. 1

        ah alright. yeah that makes sense :D

  7. 2

    This comment was deleted 4 years ago