Show HN: I've updated my food delivery repo. Feedback Welcome (github.com)
My methodology has consistently involved seeking input from platforms like Reddit and forums, where I engage with like-minded individuals. Some of the recent enhancements stem directly from this collaborative feedback, and I'm eager to gather more insights on the latest update to the project.
Designed with a focus on individuals or businesses looking to start their own food delivery services, this solution simplifies the process of adding vendors, managing food items, coordinating deliveries, and overseeing riders. Beyond these core functionalities, you'll find a bunch of other features, including order tracking, real-time notifications, and more.
Since I don’t have a substantial team backing me, I truly appreciate any assistance you can offer. Every form of contribution is valued.
Give it a star and share your thoughts in the comments section. Your support means the world to me!
33 comments
[ 4.4 ms ] story [ 73.7 ms ] threadI am trying to get my head around why set up one of these businesses when Uber, Doordash exist, and it is a network effects game, where you need the most drivers to be trusted, the drivers need to see you as worthwhile as do the customers and the restaurants. So it is not just chicken/egg but maybe hen/rooster/egg problem.
Unless your plan is selling to the well funded startups who reckon they can muscle in?
What might make a bit more sense is if this is used by the restaurant who employ their own riders, but that is a dying breed I reckon.
- Order hair and nail care services - https://enatega.com/stylizenow/
- Campus food delivery - https://enatega.com/easy-eats/ (this one is kind of just tiny bit different from normal food delivery though...)
- Wine delivery - https://enatega.com/vinifynd/
With that, I guess it kind of makes sense.
Foodora, Just Eat, Delivery Hero, Lieferando, Deliveroo, SkipTheDishes, iFood, Zomato and so on
This might be interesting from a technical perspective, but it’s unlikely that there’s a viable business model here.
As another commenter pointed out, this solution can also be used for other use cases apart from just food delivery, like wine delivery and at-home hairdressing appointments.
Lastly, we have a one time fee for the backend and we give out the source code as well. Almost every other solution is operating as saas, so this gives companies the choice to have their own food delivery management system like Ubereats without making monthly payments and with full access to the back-end so that they can customize it as much as they like.
So not open source at all then. You can't even "not open source" the frontend anyway (maybe minify and obfuscate).
The interesting part is the API and the back-end. Making the API proprietary is especially damning, it doesn't just prevent someone from hosting it themselves it prevent someone from interoperating with it. You could of course reverse engineer the API, which is why I don't quite understand the need to keep it proprietary, but having some certainty that things will simply work would be nice.
I went to the GitHub page, and on the direct link you shared, there are multiple broken images in the readme—the demo video, technology logos, etc. It is a glaring miss that within the first content of the page is a broken video. It shows a lack of attention to detail, even large details.
Next, I looked to see if there are tests/test suites for the project, as it lists working with a dozen different technologies, and I did not find one. Those dependencies will eventually have breaking changes, and with the numerous interconnected front-ends, bugs are just waiting to happen without tests.
I was curious about your license fee and navigated to the Enatega website, which is very slow. It took more than five seconds to generate the HTML page. Web best practices are the largest paint of your website. It should happen in less than two seconds, and five is off the charts.
I was curious if your company's website, Ninjascode, was any better, but it was even worse. It took 35 seconds for the server to send the HTML page.
You will lose customers because people will not spend thousands of dollars to license and trust software when the creators cannot serve a good experience on the marketing sites and don't QA their work.
That would be my overall advice: there needs to be more attention to detail. And then secondly, forming a plan to keep software error-prone as the tech stack and code changes over time.
So for most of the issues like broken images and the website being slow; our hosting server was not equipped at the time to handle a massive influx of users on the site which was what happened at the time that you would have opened it as well. (We were not expecting that much traffic to be generated from this post but yeah we should have been better prepared). The server's been upgraded now and the site should be much faster now.
I would also like to point out that we are actively working on a lot of the components for the solution, as well as the website so we know that a lot of improvements are still to be made.
This should be changed in my opinion, I wouldn't say "our solution is open source" when the backend and api aren't.
And the "enatega" site is slow (same with the ninjascode site) and broken, sometimes it loads, sometimes it gives a Database error
The twitter account linked on the Github org is also suspended so that should probably be removed
So what's exactly open source?