Do I better start developing my app at this point? blueprinting is becoming so tedious.

[genesisk5]

I have an idea for an app and I've been working on it by my self. I've done blueprinting and framing the main concepts, how each screens should look like, how they're going to interact and so on macroscopically in the recent 2 weeks but it's getting extremely tedious and exhausting tinkering with perfecting all the subtle details and amendments.

do I better finish perfecting the details (of course for an MVP) before diving into development? or would a macroscopic blueprint be enough to start development and the subtle details might follow along naturally?

edit: thank you so much guys. because the borderline of whether if it's an MVP or not is not always so definitive, I feel like I often tend to fall into the trap of overthinking because from one perspective it makes sense to make it better before launch if you can but when I step back and see from a wider view, I realize that it was a bit above MVP and that I was overthinking it. knowing to which extent is going to be within the range of an MVP is not an easy thing to me I guess.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[MJ DeMarco]

or would a macroscopic blueprint be enough to start development and the subtle details might follow along naturally?

Sounds like you are overthinking and overplanning. Dive in and then you will see exactly how detailed you will need to be. That's my take.

 

[NeoDialectic]

Start creating ASAP and figure out the details later. The most important parts to plan and build are the parts that actually give value to the customer. All the niceties surrounding it should be figured out as you go.

 

[Oso]

I'm a dev myself. Above all else, emphasize pushing your MVP out, otherwise you'll overthink yourself to the point of never launching it.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.