Technology hypothetical
Technology hypothetical
Out of context: Reply #2
- Started
- Last post
- 4 Responses
- shapesalad2
Break down what the whole business is, starting from end result.
Food at customers house
^
delivery person
^
contract for delivery person
^
app specific for delivery people
^
affiliated restaurants
^
contract with restaurants
^
negotiation with restaurants
^
... etc .. etc^
app UI / UX design
^
...
...
^
database driven app: ruby on rails- at each stage you can start to see the work requiredshapesalad
- and figure out the tech required to solve those business needs.shapesalad
- Like it.BusterBoy
- presuming a some existing business has approached you for advice on this? all your options at this point are based on budget, infrastructure, roll out.kingsteven
- is Ruby, especially on Rails, still de rigueur?detritus
- read this if you want to know the true headfuck of deliveroo's tech https://jungleworks.…kingsteven
- < i know this is meant to be simple, but the infrastructure involved in running a company like this successfully and competitively is a whole other matter.kingsteven
- if all you're offering is food taxis no restaurant will give you % cut + delivery charge when they've got a cousin that does that there ruby on rails.kingsteven
- The link to the uber Eats article at the end of that seems relevant also..
https://jungleworks.…detritus - it's clear the huge marketing budgets and co branding is everything in persuading restaurants to choose you over a competitor. deliveroo's exclusivity beingkingsteven
- a prime example.kingsteven