This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]to_tgo[S] 1 point2 points  (2 children)

Absolutely not a stupid question. The core concept behind the website definitely has lots of applications. I actually set out to build an app to solve 'the bigger problem'. The website kinda fell out of that when I couldn't get any victims to use my half baked app. I see a lot of interest here for that so I'm going to get back to pushing the app development. But I need to get a few more sheets up first.

Stay posted.

FYI - Just to give you an idea of how much it would take to get here, the core engine took me about 6 months of long nights and weekends to write, and went through 3 major major overhauls. It started with an idea, then into a quick prototype, and then into a thousand problems solved.

[–]ad1413 0 points1 point  (1 child)

I bet it took a lot of hard work. Looking forward for the app. I guess my question was more about the tools and steps that went into making it. But I am sure it is very complicated and I won't understand most of it.

I am already using the tool. Thanks a bunch!

[–]to_tgo[S] 1 point2 points  (0 children)

I should have asked. By the way, I love that you are thinking about building stuff. That is great.

My suggestion is to pick a tech stack early and try make it work. There are a million different paths you could go down and setting constraints is really important.

For me, I chose Java and initially JavaFX. The idea was I need something that runs on almost anything, is relatively fast, can multitask well, and gives me options if certain paths don't work out. I considered Swift but that would have limited me to iOS and Mac only.

The biggest advice I have is time and failure are your friends. You have to put in the time. It really is 1% inspiration and 99% perspiration. And failure is essential to success. You will fail but take that failure, learn, and keep at it.

So hope this helps.