- Thread starter
- #20
User Power
Value/Post Ratio
65%
- May 30, 2011
- 387
- 253
Got it. So do I. I was just curious why you wouldn’t opt to build your application with a foundation that’s easily scalable for future iterations. It’d suck to turn this project into something bigger and need to go back and change your entire frontend.
Sometimes more work upfront saves a lot down the line.
I have similar beginnings as you, so kudos on getting it done and teaching yourself.
I hear you on the upfront investment / backend payoff point. The idea I have is this - get a simple idea making money first, and if I can get it to that point with the smallest possible upfront investment, then it'll be worth updating the frontend if that's necessary, and at that point I'll know it's worth it.
The mysterious guy I mentioned in my OP started a publishing business on Wordpress lol. He wrote the theme himself and launched. It caught fire, and at that point he build the entire thing again in Rails to his exact needs. That's a similar approach I'm taking here. Because the upfront cost with the unknown payoff is the biggest motivational detriment I have right now. I spent an absurd amount of time on a meal plan application, so long that I couldn't push to make it work when I started marketing it. I just gave up, especially when I saw SPREADSHEETS going viral and some weird google algorithm that could do what my app did but 10 times better AND the UI was totally confusing and horrible.