I have a project in my head and I want to understand the tech needed to build it
I wanna build this marketplace which I made a submission earlier and talked about it and now i wanna understand if it's technologically feasible and the skillset needed to build it. How can I do it?
16 comments
[ 5.1 ms ] story [ 55.0 ms ] threadIf you do manage to find a niche, then you're invited to a whole new circle of hell in fraud mitigation and chargebacked invoices. You need a really good idea to break into the current scene.
Initial ideas are easy, execution is harder, and maintaining it across time and devices and changing tech is very hard. Delivering static things like books or phone cases or laptop chargers is one thing. Delivering food is a completely different ball game.
I agree with your overall sentiment though, we'd all be better off if our food originated nearer to us and we had the proper systems to make local food more profitable for smaller food producers. But Amazon, WalMart, Costco, Hello Fresh, Full Circle, Blue Apron and dozens of other very deep pockets make it very difficult to keep up. You have to be better at something besides price or convenience, because they're run circles around you with those two. For example, you have certain advantages when you're "small" that an Amazon just simply can't compete with. Things like quality, small quantities, hyper-local, hyper-fresh, customer service, high-touch items, etc. Amazon has disadvantages because of their scale, so lean into those areas that don't scale to get some traction.
This still stands. How many potential customers have you since talked with to de-risk the very "market existence" aspect first?
Why? It doesn't have to be the idea itself. You can ask questions to check whether it is a problem first as opposed to talking about your solution. What if they're not aware it's a problem, or don't care about it? It's harder to sell a solution to a problem to someone who is not aware of the problem or does not care about the problem than it is to someone who's well aware, who cares about it, and who's tried to solve it but failed.
>and because my app would require some kind of technical infrastructure i don't wanna start talking with local restaurants.
Why?
>i feel like i can convince the big boys and the locals would follow them.
Feel? Wouldn't having actual conversations and learning things that are invisible to you right now beat that and shed light on many things?
So? You'll talk with many people you didn't personally know. Case in point, we're having this conversation.
>2. i want restaurants to keep their menus and kinda "host" their menus themselves. and i won't be providing any customer service or something like that. because of that, i want corporate restaurants have tech infrastructure.
I'm sure you have reasons that lead you to this, and I'm sure you'll learn many things talking with people in the field.
>3. my only concern is about the product
So many built the best product people never used.
Please get out there and talk with people in a way they'll tell you about their problems and what they've done to solve them or not.
What would you say, if you probe a little bit and get a slight understanding of problems, and then, learn how to code just that. Little by little, you learn and stay motivated because you're converging towards something real.
However, if you are completely indifferent to the outcome, then by all means, go ahead; programming is fun for its own sake. It's just that the premise of this conversation was misleading.