How do you develop your applications?

Question

Mobile development

A question for solo founders, if any, are sitting on the site.
You've got another billion-dollar idea. You are determined to carry out the project, but so far, apart from an abstract idea, there is nothing. Your actions?

Interested in the flow of experienced developers. Personally, I give up all my attempts halfway, because I don’t know how and where to move on. It seems that there is an idea, the TK is more or less described in Google docs, there seems to be a nice layout in Adobe XD, there is even an almost working version of it on Vue, and even, some kind of server, and you can already perform some actions. There are even Jira/Trello with puzzles. But when you want to write code, you understand that it is better to finish the design first. You climb into the layout, you understand that you don’t understand shit - there is no idea what elements should actually be on this page. As a result, you return to the TK and squeeze a couple of lines out of yourself and put off all attempts to do something for another couple of weeks.

But everything is in this state and freezes when the ardor of the original idea fades away, when you realize that it is generally too complex and complicated and you can’t solve it “at a glance” - after all, in large companies, entire teams of designers, analysts and products are struggling with such things. not to mention the developers.

So. What is the best way to lead projects alone? How to structure all the data and not drown?

Answer 1

I'm assuming here that you want to make some kind of worthwhile product that someone needs:

You've got another billion-dollar idea. You are determined to carry out the project, but so far, apart from an abstract idea, there is nothing. Your actions?

Roll over to the other side and sleep on. An abstract idea worth a billion is worth nothing, not even 10 minutes of your time. A hundred abstract ideas is just a hundred times more wasted time.
If you strongly believe in some idea, for starters, you validate it.

you understand that you don’t understand shit - there is no idea what elements should actually be on this page.

You almost get the point here. Your "idea" should tell you what elements are needed, why they are needed and why exactly they need to be done right now and not something else. While this is not there, you do not have an idea, but some kind of vague fantasy, you do not know what you are doing, and it is unlikely that you will do something.
Learn everything you can about building a product. There are many approaches, information too.
the problem is that this is a completely different area, you are a beginner there and zero without a wand, you need to put a lot of effort and if you are not interested in it, then the brain will actively resist. There will always be a temptation to take and file some code instead, come up with buttons, throw tasks into a Trello - it's simple and clear.
There are two options here - find a co-founder who will move this side, and leave the realization for yourself, or overpower yourself and learn the necessary skills.

Answer 2

A very small number of people can make a product alone. I have the same problem. The solution is to find a person with whom you can discuss your decisions and get confirmation that everything is cool and can be implemented. You lack approval from third parties perhaps

Answer 3

If the problem is too complex, simplify. Choose the simplest thing that you can implement and "sell" to potential users. And do it continuously, then you will get feedback from potential users. And this will be some first real result.
Everything else is a waste of time and effort. Even these mockups. You don't need to work on layouts, TK, idea -> do something, somehow. Show results to users. Start selling it.

Answer 4

Rework

Answer 5

I use TDD. Without tests, I don’t understand at all whether I did the task or not yet, and everything around seems unfinished. Here I divided a large task into a number of small ones, wrote tests, wrote code, and you clearly feel the moment when you can move on to the next task. But I'm not in release, so I'm a bad example, because I'm doing it because it's interesting to make an infinitely scalable full-websocket application using 3d and layered architecture from all these smart books on object-oriented programming, and not because I'm hungry for a billion. During this time, I have already lost count of how many I changed frameworks, databases, and even changed the language in the end. During this time, AngularJS (the one that 1.x) managed to be born and die, and I write everything :)

Answer 6

I always try to completely "soak" in the spirit of startup (let's call it that), you need to think about the project for several days, its pros and cons, and on the second day in 90% of cases you will understand that the idea is stupid or not new. This is necessary to solve the main problem of development in one person, the problem of losing interest in the project. When you really get excited about the project, then everything will go by itself, and the main thing to remember is “Moscow was not built right away”, you will constantly fail to get something, because you take on the work of several people, and you need to look at problems from positive :)

Answer 7

3 is more or less described in Google docs

A typical mistake of home destroyers of the world.
The second mistake is to start with design.
Design and layout - this is the last thing that should be in the project.

Answer 8

1. Every day or regularly remind yourself that the solution of any more or less valuable task takes five or even ten times more time than it initially seems.
2. Break a complex task into many simple ones, and slowly finish them off. An elephant must be eaten in parts, in small pieces.

Answer 9

You either do something, or you come up with reasons, excuses.
All skills come only with experience, there are no geniuses and momentary results.
Everything is extremely simple.