not approved
Hungry Haste: decentralized and open-source food pickup and delivery service
Current Project Status
Unfunded
Amount
Received
₳0
Amount
Requested
₳500,000
Percentage
Received
0.00%
Solution

We replace traditional apps with open-source apps and decentralized finance. It helps to reduce the price of an average pickup order by 15-30%. Later, we’ll add food delivery and better drivers’ pay.

Problem

Apps like DoorDash charge 15-30% fees on food orders. As a result, the price of an average order skyrockets, but delivery drivers still often struggle to earn even a minimum wage.

Logo

Screenshot-f417e7.png

Impact / Alignment
Feasibility
Value for money

Team

3 members

Hungry Haste: decentralized and open-source food pickup and delivery service

Please describe your proposed solution.

The background:

When Grubhub, UberEats, DoorDash, and other similar food delivery apps were introduced, they brought an effortless and convenient way to order food by choosing from one of the many available restaurants nearby. Nothing like that has ever been possible before. Unsurprisingly they immediately attracted millions of users worldwide. The audience capture was so impactful that if a restaurant wanted to attract customers, they had to be on one of the platforms and had to sign any draconian agreements the app overlords would offer them to sign. Each of those apps is a great tool. But in the hands of corporate middlemen, slowly, step by step, they imposed enormous fees on the restaurants. The restaurants eventually passed the costs to the customers. And instead of decreasing their fees, the apps cut the expenses by lowering earnings for those who are the least in control - the delivery drivers, who often struggle to get even the minimum wage.

The problem:

  • Revolutionary tools like the Internet and food-ordering apps helped a few individuals to monopolize the market.
  • A small group of people in charge of the apps is driven by self-interest, which results in high restaurant fees and low driver pay.
  • The audience capture and convenience of the apps don't leave many options for restaurants and delivery drivers.

The reasons behind decentralization and how decentralization can fix the problem:

While those apps are great tools, and their creators deserve the rewards, we believe the Internet and software should help to create a better society instead of helping centralize power and resources in the hands of a few. By providing open-source solutions and decentralized infrastructure based on Cardano, we can eliminate unnecessary middlemen in the process, drastically reduce high fees, reduce the overall cost of each order (especially pickup orders), and significantly increase drivers' pay. Additionally, by leveraging the token economy philosophy, we can find new ways of monetization for the builders and early adopters.

Centralized entities like banks, music labels, insurance companies, food delivery apps served their purpose in the 20th century. They all were the best solutions available. The blockchain, however, gives us a completely new toolset. And it opens new possibilities and provides better solutions to deal with the problems our society faces. Cardano-based projects like ProjectNEWM help to eliminate the music labels from the equation and provide a more fair redistribution of the profits among music artists. We can do the same in the food delivery industry by eliminating high fees on pickup orders and redistributing locked profits among drivers on delivery orders.

Which problems can be solved in food ordering?

  1. We can significantly decrease fees on pickup orders by removing centralized entities from the equation.
  2. We can increase drivers' pay by sending all the fees directly to drivers instead of the app owners.

Both problems are important to solve. But we believe it's better to handle one problem at a time. We will start by reducing fees on pickup orders. This problem is easier to solve, requires less funding, and we can prove that our idea is working. Plus, 75% of all food orders in the US are pickup orders. While the app can be used in any country, we will launch in California - one of the most popular places for food ordering on Earth. When thousands of customers and restaurants already use the system and transact on the Cardano platform, adding drivers and food delivery will be much easier.

Important: This funding will help us to implement a solution for pickup orders. The driver app and delivery orders are not included in this proposal. While we mention our plans for drivers and delivery orders in this proposal, this problem is harder to tackle. Let's handle them one at a time and deliver a strong proof of concept first.

The solution:

The solution will benefit all participants in the food pickup process. Restaurant fees go to zero. Customer fees become significantly lower than in any other available service. Drivers get 100% of the delivery fees. Participants will also receive our utility token for different actions they perform for the network. Smart contracts will transparently redistribute the earnings between restaurants, drivers, customer support members, and builders. We will also use our utility token to measure everyone's involvement in the project. There won't be any sale of the token. The token will be paid for different types of work performed for the network, so there is no expectation of profit derived from the efforts of others. The token will be used for governance purposes, and the participants will be able to vote on the network's decisions, like whether we should pay more to drivers or reduce delivery costs for customers. Additionally, tokens will be used to purchase different priveledges in the system, so those participants who proved their understanding of the internal works of the system will be able to gain a slight advantage over newcomers.

An interesting side effect of the utility token and the fact that all our apps are open source: people will be able to clone the code and span multiple delivery services competing with each other with different governance settings. Some can provide better pay for drivers, and others can vote for higher user discounts. The best approach will win.

The solution consists of multiple apps and smart contracts:

  • Web App. The web application is available in your browser to order food and find restaurants near you.
  • Mobile App. Mobile apps for iOS and Android provide a seamless transition from apps like DoorDash to our new app. Our team has a UX designer responsible for user research and ease of use. We put extreme emphasis on simple transition, even for people who have no idea what Cardano and cryptocurrencies are. We will leave an option to pay in fiat. Fiat currencies will be internally converted into ADA so that every fiat transaction will be a transaction on the Cardano platform. But the users who use Cardano and ADA will gain immediate benefits and better offers. We hope it will motivate more people to understand the ecosystem and gradually switch from fiat to ADA.
  • Restaurant Admin Panel. Every restaurant will be able to access the app that will notify them when new orders come in. The app will also allow editing their menu and other information.
  • Customer Support Admin Panel. The web app will help to manage the system's data, track the status of the orders, cancel orders when needed, onboard new restaurants, and so on.

Parties and how they benefit from the system:

  • Customers. Customers will benefit from eliminating restaurant fees on pickup orders, resulting in huge discounts. The discounts are parameters in the system that are governed by the utility token and can be changed by the community to achieve the best experience for all parties. We will almost eliminate fees and leave a minor fee (10 times smaller) to support builders and customer support members.
  • Restaurants. We will entirely get rid of restaurant fees.
  • Builders. Builders will be rewarded with the minor fees paid by the customers and the utility token's monetary expansion.
  • Drivers (Future Versions, not included in the current scope). Drivers are the second primary beneficiary of the system. We plan on the biggest chunk of the profits going to the drivers. However, the distribution of the earnings in the system will be governed by the utility token and can be changed in the future by the community vote.

<u>Web App Map: </u>

Web App Map

<u>Web App Menu:</u>

Web App Menu

<u>Mobile App Restaurants:</u>

Mobile App Restaurants

<u>Mobile App Menu:</u>

Mobile App Menu

<u>Restaurant Admin Panel:</u>

Restaurant App

Restaurant App 02

How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

The proposed solution is a marketplace that can attract hundreds of thousands of active users to the ecosystem. Let's look at DoorDash as a competitor and analyze some of the DoorDash statistics:

  • DoorDash generated $6.58 billion in revenue in 2022, a 34% increase year-on-year
  • DoorDash had 32 million active users who use the app at least once a month
  • Doordash has more than 390,000 grocery markets and partnered restaurants on its platform.
  • Doordash is available in over 4000 cities in North America.
  • 75% of all food orders in the US are pickup orders

Even if we can attract only 1% of their audience, it's already 320k orders per month. And nothing sells better than the idea of a 20% discount on everything. We believe even a minor investment in marketing can attract enough people to make it worth the investment.

Benefits for the Cardano platform:

  • Even assuming a minimal success of the app, it will attract thousands of users to the platform.
  • The ability to use fiat that’s converted into ADA internally will add even fiat-based users to ADA transaction statistics and will help easily onboard new users.
  • We will conduct professional UX research. One of our top priorities is the easy-to-use interface. We believe it will help attract a new audience who didn't know much about crypto before.
  • The product will be a perfect example of how the blockchain can change the way people conduct online business using open-source software. And this example will be built on Cardano.
  • It's perfect timing for an app built with governance in mind. Cardano is at its latest stage of development. Governance has become more important than ever. Cardano has all features we need to make the app succeed. There is also a high chance of a bull run around the moment of our launch. Rewards in the form of utility tokens will be very attractive to the customers.
  • Cardano will have one more real-world applicable use case with a real-world utility that is easy to understand for non-tech people.
  • We will use the Cardano logo on every delivery and pickup food bag just because it is cool!!!

How do you intend to measure the success of your project?

We need to establish metrics so that if we succeed in each of them, it would mean the automatic success of the project.

Let's define the target goals first:

  • Our apps should be up and running and bug-free
  • Target areas are chosen based on available food order statistics
  • Restaurants in the target areas are integrated with our system
  • Customer support is up and running
  • A Cardano-based utility token is integrated into the system
  • Become profitable, so we don't need an investment for the second part of the project (integration of the drivers)

Based on the target goals, we need to track progress for the following metrics:

  • Number of restaurants we onboard in selected areas monthly
  • Number of transactions conducted in the system monthly
  • Number of users converted from fiat to ADA and using crypto wallets directly
  • Average revenue per customer
  • Customer acquisition cost: how well do our marketing campaigns perform?
  • Customer conversion rate and A/B Testing
  • Customer churn rate: how often do customers return?
  • Customers Feedback: App Store reviews, Freshdesk requests, Customer support queries
  • Restaurant conversion rate: how easy is it to onboard new restaurants?
  • Restaurant churn rate: why do we lose some of the restaurants?
  • Social Media Engagements
  • SEO performance: how many unique visits do we get from search engines?
  • Cardano community feedback: is there anything we can do to add even more value to the Cardano ecosystem?

Please describe your plans to share the outputs and results of your project?

We pursue the following goals when we share the results of our work:

  • We want to understand what can be done better to improve our users' experience.
  • We want to know how we can help the Cardano community and platform to grow.
  • We want to share our updates and announcements.
  • We want to show the community that we meet the deadlines and deliver on our promise during every milestone.
  • We want to be able to make accurate predictions and estimations about the future of the project based on growth metrics.
  • We want to find new possible collaborations inside the Cardano community to help each other and the platform grow.
  • We want to increase awareness and publicity for the project and the Cardano platform.
  • We want to gather insights from experts in the industry and outside of the industry.

For every of the described goals, we can define detailed steps for sharing the results and outputs of our project:

<u>1. We want to understand what can be done better to improve our users' experience</u>

We want to engage with our audience in the most transparent and informative way. And we want our audience to be able to discuss our project and share their ideas openly. The online community on Discord, Telegram, and Social Media will help to exchange ideas and get real-time feedback from restaurants, customers, drivers, and the community. We will convert the gathered feedback from the online groups and our Freshdesk tickets into Github proposals.

<u>2. We want to know how we can help the Cardano community and platform to grow</u>

We will engage with the Cardano community through the same online channels (social media, online chats, and groups). But also through conferences and online and real-life events and Q&A. The ideas and suggestions will be converted into Github proposals.

<u>3. We want to share our updates and announcements</u>

Social media, online chats, our website, and our blog will help to share updates with the community. Participation in startup-oriented podcasts, YuoTube video blogs, and industry-specific conferences can help share the details outside the community and spread the word.

<u>4. We want to show to the community that we meet the deadlines and deliver on our promise during every milestone </u>

Publicly available Scrum boards with task statuses and estimations will help the community understand the project's state and how close we are to promised results.

<u>5. We want to be able to make accurate predictions and estimations about the future of the project based on growth metrics.</u>

We will share our current metrics and statistics of growth in the publicly available dashboard. Revenue, customers and restaurants acquisition and churn rates, and other metrics (see "How do you intend to measure the success of your project?" section for reference).

<u>6. We want to find new possible collaborations inside the Cardano community to help each other and the platform grow</u>

Collaboration with other Cardano projects is essential and can help leverage the experiences of each other to grow. We will prioritize real-life meetings and constant online collaboration through mediums like Twitter Spaces or one-on-one calls and meetings with leaders of other projects.

<u>7. We want to increase awareness and publicity for the project and the Cardano platform.</u>

We will publish research papers, guest articles, and case studies. Participation in startup-related podcasts and YouTube vlogs can help attract founders and investors outside the Cardano community. The same can be said about participation in conferences, tech, and industry-related events.

<u>8. We want to gather insights from experts in the industry and outside of the industry.</u>

The priority is networking and meeting new people with an influence outside of the Cardano community and sharing our vision and story and how the Cardano platform helps to build decentralized businesses in an innovative way. Sharing the necessity of strong basics, decentralization, and a strong community behind the web3 project can explain why Cardano is better than other platforms.

What is your capability to deliver your project with high levels of trust and accountability?

A short answer:

  1. We already have approximately 50% of the product built.
  2. We are a team of 25 specialists with expertise in web and mobile app development. We have backend and frontend engineers, DevOps and SecOps specialists, project managers, and professional UI/UX designers in-house.
  3. We have Haskell and even Plutus school in-house.
  4. We are a software development agency with 7+ years of experience built from zero without any funding or connections at the time. Managing funds is our second job.
  5. We are totally fine with being paid upon delivery of every milestone instead of being paid upfront. We work this way for almost 8 years. We have a one-month trial period for all our clients because we are confident in our ability to deliver.
  6. Our location is perfect for the project. Our main office is in California - one of the biggest markets for food ordering in the world.
  7. But many of our engineers are also located worldwide (mainly in Eastern Europe and the US, but also in Latin America and Central Asia). That helps to keep our costs reasonable.

A long answer:

<u>1.We already have approximately 50% of the product built.</u>

We've been running a food delivery service in Belarus between 2014 and 2016. Unfortunately, because of the political state of things in Belarus, we were forced to close our service there, and instead, we opened a software development agency. We feel the pain of the centralized solution being shut down by the government in our hearts :)

But we still have the source code we used: web portal, restaurant admin panel, driver's app, admin panel, and API. The source code is outdated and requires an update. We didn't have a mobile app or even a mobile version of the website because of the user preferences to use a web browser on a big screen in Belarus back then. The UI/UX needs a new and fresh look (which we already designed too).

You can find the next links in the links section:

  • The old desktop version of the website: <https://test.hungryhaste.com/>

Use credentials: delivery / 123456Qq.

Please keep in mind: all update and delete operations are temporary locked for the test account

  • Admin Dashboard: <https://admin-test.hungryhaste.com/>

Use credentials: SystemAdmin / 123456Qq.

Please keep in mind: all update and delete operations are temporary locked for the test account

What do we still need to build?

  • Update the design of the website (we already have mockups)
  • Update web app and API logic to meet the US market requirements
  • Build the mobile app
  • Update the restaurant app to follow the US regulations and to be able to integrate it with popular POS systems in the US
  • Implement smart contracts, integrate the utility token, and move half of the operations to the blockchain

<u>2. We are a team of 25 specialists with expertise in web and mobile app development.</u>

You can learn more about our team here: <https://www.devteam.inc>. We have backend and frontend engineers, DevOps and SecOps specialists, project managers, and professional UI/UX designers in-house. Please check the video of some team members saying "Hi!" in the links section!!! We can start immediately. We already have all the team members we need, including Plutus developers and even the UX designer who will help us build an easy-to-use web3-based system.

<u>3. We have Haskell and even Plutus school in-house.</u>

As a software development agency, we also offer Web3 software development services. And we have our own internal Plutus school (based on the amazing Plutus pioneer program by Lars Brünjes). We already have engineers who we need to deliver the smart contracts.

You can find more info here: <https://cardano.devteam.inc/>. It's the page of our pool that we plan to use soon to teach students Plutus. This project is a work in progress and self-funded. We didn't have a chance to finish it yet.

<u>4. We are a software development agency with 7+ years of experience</u>

We have extensive experience in web and mobile app building and budget management. We don't have external funding, so we have to rely on constant cash flow and be aware that clients come and go, but we don't let our people go even in the most challenging situations.

<u>5. We are totally fine with being paid upon delivery of every milestone instead of being paid upfront.</u>

We work like that for almost 8 years. One of the main features that you can find on our website is that we provide a one-month trial period. We are confident that we can deliver on what we promise.

<u>6. Our location is perfect for the project. Our main office is in California </u>

The US and, specifically California, is one of the world's biggest markets for food pickup and ordering. Los Angeles, Bay Area, San Diego, and Sacramento are all top places by the number of orders on DoorDash. It means it is much easier to make the project profitable and then expand to other regions of the world.

<u>7. Many of our engineers are also located worldwide</u>

We have a small team in the US, Los Angeles. But most of our members are in Eastern Europe, Poland. This combination of engineers across different time zones helps to keep costs reasonable and makes it possible to deliver projects much cheaper than many other companies.

What are the main goals for the project and how will you validate if your approach is feasible?

The main goals of the project can be defined as follows:

  • Eliminate the middlemen in food delivery services and reduce food order pickup fees by approximately 20% compared to apps like GrubHub, DoorDash, and others.
  • Introduce the utility token that will be used to govern the system and will be a guarantee that the fees can not be increased in the future without community approval.
  • Create a system based on professional UX research where even people who don't understand the crypto and blockchain can benefit from the token economy.
  • Achieve profitability and be able to develop the system without further funding. We need approximately 100,000 orders a month to break even. That also results in 300,000 transactions on Cardano for a standard pickup order.
  • Convert at least 30% of users from using fiat to ADA.

Most of our objectives can be easily quantified. The idea itself is not new, and we know that food delivery apps are very popular. If we can deliver apps that won't require any additional effort from the customer or restaurant, it will be the same service they already use but cheaper.

Thus the challenges are:

  • Implement a system where even if users use fiat, it still triggers ADA transactions and doesn't impose any tax implications on the end user. Feasibility can be verified during the first milestone, even before the apps are delivered. We only need to implement a couple of smart contracts and API endpoints.
  • Prove that reduced fees and the utility token provide enough incentives to maintain the system. If the system can attract at least 1% of GrubHub or DoorDash users, it is already a profitable system and a very attractive endeavor for most entrepreneurs and builders.
  • Provide enough incentive for people to switch from fiat to ADA over time. Even if we fail at this objective, we will still have hundreds of thousands of ADA transactions monthly. However, we want people to learn more about crypto and the Cardano platform. Transactions that don't involve fiat will be even cheaper than fiat-based transactions, plus we will provide additional benefits of staking rewards. We will measure the fiat-to-crypto conversion rate and experiment with different ideas.

The rest of the project is pretty straightforward and depends on implementing the web and mobile apps. Restaurants are already familiar with these types of apps and will be happy to get rid of the fees. Customers who use GrubHub or DoorDash will be glad to reduce their bills too.

Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

To deliver the project, we need to deliver the following top-level pieces of infrastructure:

  • The utility token, tokenomics, smart contracts, and the ability to convert fiat-to-token and back in a transparent manner
  • Secure API to provide an easy way to communicate with the system
  • Admin Panel for customer support, accounting, and data management
  • Restaurant App for restaurants to manage their data and receive/process orders from customers
  • Web App for anyone to search for restaurants and food and to order the food
  • Mobile Apps as a more convenient way to search for restaurants and to order food from your phone
  • Professional UI/UX Research and Design of every app, especially customer-facing Web and Mobile apps
  • Open Source repositories and dashboards for project progress, issues, and proposals tracking
  • DevOps for a convenient and easy way to perform autotests, check the quality of the code, deploy code to different environments, and scale the infrastructure on-demand

We plan to deliver each of the features in 8 milestones. Every milestone is approximately one month. It should help the community to validate our progress, our deliverables, and how we meet deadlines.

Every milestone will be divided into one-week sprints. We will use Scrum to deliver the project on time and without bugs. Our test environment will be automatically updated daily. Our staging environment will be updated weekly with the results of every sprint.

Milestone 1: Working environment and infrastructure set up

Duration: 4 weeks (1 month)

Tasks:

  • Publicly available scrum board and weekly sprints
  • Continuous Integration and Delivery pipeline to automatically deliver code updates on a daily basis
  • Test, Staging, and Production environments for the web app, mobile apps, admin panel, API, and the restaurant app
  • Legal consulting: the restaurant and customer agreements, terms and conditions, etc
  • The utility token whitepaper and tokenomics. Minting of the token.
  • Setting up a Stripe account for Fiat payments
  • Web App architecture (the core functionality and decisions)
  • Mobile App architecture (the core functionality and decisions)
  • Restaurant App architecture (the core functionality and decisions)
  • Admin Panel architecture (the core functionality and decisions)
  • API architecture (the core functionality and decisions)
  • The centralized data storage setup: migration of existing data structure from MS SQL to open-source PostgreSQL database
  • Social Media, online chats, and other communication channels
  • Pick target areas with the highest expected amount of orders based on available statistics

Acceptance Criteria:

  • "Hello, world" versions of every app should be automatically uploaded to the test environment daily and to the staging environment weekly, including to the Android and iOS app stores.
  • Legal documentation is ready and available as a public service agreement for anyone.
  • The utility token is minted, and the whitepaper is ready.
  • Communication through social media, online channels, and the Scrum dashboard in GitHub is up and running.

Outputs and Evidence to validate the acceptance criteria:

  • Basic web app functionality is available to anyone on test.hungryhaste.com and staging.hungryhaste.com.
  • Android and iOS apps-placeholders are available as alpha versions via Google Play and App Store.
  • Admin panel app should be available to anyone on admin-test.hungryhaste.com and admin-staging.hungryhaste.com.
  • Restaurant apps-placeholders are available as alpha versions via Google Play and App Store.
  • The code of all of the apps should be open-source and available in the GitHub repositories.
  • API core functionality should be available to anyone via api-test.hungryhaste.com and api-staging.hungryhaste.com.
  • Legal agreements with customers and restaurants can be found in the website's footer as a public service agreement.
  • The utility token is minted.
  • The whitepaper with described tokenomics can be found in the website's footer.
  • Daily updates and community engagement on Twitter and in online channels.

Costs: 42,000 ADA or 8.4% of the Grant Amount

Milestone 2: Restaurants onboarding process development

Duration: 5 weeks (1 month and 1 week)

Tasks:

  • API functionality:
  • admin authentication
  • Restaurant management: add new, update the info (description, phone numbers, addresses, working hours, photo, type of the food, and so on)
  • Menu management: add/modify/delete products and their available sizes and ingredients
  • Payments to restaurants (no code at this stage, just adding Stripe accounts and Crypto wallets to the system) for all 4 cases:
  • The customer pays in fiat; the restaurant receives money in fiat.
  • The customer pays in crypto; the restaurant receives money in fiat.
  • The customer pays in fiat; the restaurant receives money in crypto.
  • The customer pays in crypto; the restaurant receives money in crypto.
  • Admin Panel:
  • Restaurant management functionality: add/modify/delete.
  • Menu management functionality.
  • Photos upload.
  • Working hours.
  • Available ingredients.
  • Categories of the food.
  • Restaurant App:
  • Authentication
  • Ability to edit its own information: contact details, working hours, etc
  • Menu, ingredients, categories management
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity

Acceptance Criteria:

  • At this point, we should be able to add new restaurants into the system via the API and our Admin Panel.
  • Restaurants should be able to edit their own information via the mobile app.
  • Restaurants can receive the payments in fiat and crypto (the infrastructure is in place - Stripe , but no functionality in the apps yet)

Outputs and Evidence to validate the acceptance criteria:

  • Anyone should be able to add new restaurants through admin-test.hungryhaste.com and admin-staging.hungryhaste.com or via API at api-test.hungryhaste.com and api-staging.hungryhaste.com using publicly available test and staging credentials.
  • API documentation should be publicly available.
  • Anyone should be able to query existing restaurants via api-test.hungryhaste.com, api-staging.hungryhaste.com, and api.hungryhaste.com (the production environment)
  • Anyone should be able to download the Android and iOS apps for restaurants and play with publicly available data for test and staging versions. Also, anyone can add their restaurant to the production environment, but they won't get approval without a real restaurant.
  • Demo video with the presentation of the restaurant onboarding process.
  • Demo video showing auto-generated Stripe accounts and Crypto wallets for the added restaurants.
  • Daily updates and community engagement on Twitter and in online channels.

Costs: 70,500 ADA or 14.1% of the Grant Amount

Milestone 3: Create order functionality

Duration: 4 weeks (1 month)

Tasks:

  • API functionality
  • Ability to create/modify/cancel order
  • Track the order status
  • Admin Panel functionality:
  • Ability to track submitted orders
  • Ability to manage the order status and cancellations
  • Restaurant App functionality:
  • New order notifications
  • Detailed order and customer information
  • Order status updates and cancellations
  • Payments are received by the restaurant to their fiat or crypto wallets.
  • Fiat transactions are just a facade and trigger crypto transactions and the code on the blockchain.
  • Restaurants onboarding in the target areas
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity

Acceptance Criteria:

  • We should be able to create new orders via API.
  • The payment should be sent to the restaurant via fiat or crypto.
  • Every payment, including fiat payments, should trigger crypto transactions on the blockchain (but no smart contract at this stage, just simple transactions).

Outputs and Evidence to validate the acceptance criteria:

  • Anyone should be able to create / modify / cancel orders and query the order's status via api-test.hungryhaste.com and api-staging.hungryhaste.com using publicly available test and staging credentials.
  • Even if we pay with fiat, we still should see the ADA or our utility token transaction in the blockchain explorer.
  • API documentation should be updated and publicly available.
  • Anyone should be able to query existing restaurants via api-test.hungryhaste.com, api-staging.hungryhaste.com, and api.hungryhaste.com (the production environment)
  • Anyone should be able to download the Android and iOS apps for restaurants, receive incoming orders, and track / update their status on test and staging versions.
  • Live presentation showing the entire process of ordering via API and how real restaurants receive and process the order on the production environment. We should demonstrate all 4 payment scenarios: fiat-to-fiat, fiat-to-crypto, crypto-to-fiat, crypto-to-crypto. Every scenario should trigger the transaction on the Cardano platform.
  • Daily updates and community engagement on Twitter and in online channels.

Costs: 56,250 ADA or 11.25% of the Grant Amount

Milestone 4: Customer Apps: login, sign-up, and account management

Duration: 4 weeks (1 month)

Tasks:

  • API functionality
  • Customer authentication: sign-in, sign-up processes
  • Account management: Forgot Password, Reset Password, address management, contact details, add a credit card (no crypto wallets at this stage)
  • Web App functionality:
  • Customer authentication: sign-in, sign-up processes
  • Account management: Forgot Password, Reset Password, address management, contact details, add a credit card (no crypto wallets at this stage)
  • Mobile App functionality:
  • Customer authentication: sign-in, sign-up processes
  • Account management: address management, contact details, add a credit card (no crypto wallets at this stage)
  • Restaurants onboarding in the target areas
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity

Acceptance Criteria:

  • Users should be able to create their account using the web app or via Android / iOS apps
  • Users should be able to manage their account data using any of the apps
  • Users should be able to add their credit cards to the system (no crypto wallets at this stage)

Outputs and Evidence to validate the acceptance criteria:

  • Anyone should be able to create customer accounts on hungryhaste.com and via mobile apps for Android and iOS.
  • Anyone should be able to modify their customer profiles on hungryhaste.com and via mobile apps for Android and iOS.
  • Anyone should be able to add their credit cards on hungryhaste.com and via mobile apps for Android and iOS.
  • Daily updates and community engagement on Twitter and in online channels.

Costs: 42,000 ADA or 8.4% of the Grant Amount

Milestone 5: Customer Apps: Payments

Duration: 5 weeks (1 month 1 week)

Tasks:

  • Integration with crypto wallets in the Web and Mobile apps.
  • Ability to pass all 4 payment flows (fiat-to-fiat, fiat-to-crypto, crypto-to-fiat, crypto-to-crypto)
  • There is no ability to create an order via User Interface at this stage, so we will simply add input with an amount we want to send
  • Smart contracts implementation and testing. Fees are becoming part of smart contracts and can be voted on. Some of the restaurant data is moved to the smart contracts (we will use parameterized contracts and store small pieces of the data in the datum of a contract), creating a partially decentralized database of restaurants.
  • Restaurants onboarding in the target areas
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity

Acceptance criteria:

  • There is a possibility to enter the amount in the web app that we want to send via fiat or crypto.
  • There is a possibility to enter the amount in Android and iOS apps that we want to send via fiat or crypto.
  • Every transaction triggers the smart contract.
  • Fees are encoded in the smart contract logic and can't be changed in a centralized way opening the door for governance implementation.

Outputs and Evidence to validate the acceptance criteria:

  • Users should be able to connect their crypto wallets to their accounts and send crypto payments by manually entering the amount via hungryhaste.com or Android and iOS mobile apps.
  • Users should be able to use their credit cards and send fiat payments by manually entering the amount via hungryhaste.com or Android and iOS mobile apps.
  • Every payment should cause the smart contract execution on the Cardano blockchain.
  • Daily updates and community engagement on Twitter and in online channels.

Costs: 70,500 ADA or 14.1% of the Grant Amount

Milestone 6: Customer Apps: Search functionality

Duration: 4 weeks (1 month)

Tasks:

  • API: search functionality based on the customer proximity and search criteria
  • Web App:
  • UI redesign
  • Implementation of a new landing page
  • Implementation of the search functionality
  • Restaurant page and information (including the menu and categories)
  • Mobile Apps:
  • Search functionality implementation
  • Restaurant page and information (including the menu and categories)
  • Restaurants onboarding in the target areas
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity

Acceptance Criteria:

  • Users can enter their current location and see the closest restaurants in their area.
  • Users can filter the restaurants by categories of food.
  • Users can click on every restaurant and see detailed information about the restaurant, including its location, contact details, working hours, and the menu.
  • The above functionality should be available on the web and Android and iOS apps.

Outputs and Evidence to validate the acceptance criteria:

  • Users should be able to search through the list of onboarded restaurants via hungryhaste.com and Android or iOS apps.
  • Every restaurant should have a detailed description and information, and its menu with a list of the products.
  • Daily updates and community engagement on Twitter and in online channels.

Costs: 56,250 ADA or 11.25% of the Grant Amount

Milestone 7: Customer Apps: Place an Order and Cart functionality

Duration: 4 weeks (1 month)

Tasks:

  • Web App:
  • UI redesign of the cart
  • Ability to select custom ingredients for the selected menu items
  • Ability to choose different menu items and add them to the cart in different sizes
  • A detailed breakdown of the costs and fees (including fiat-based fees to attract more people to move away from fiat and get even better deals)
  • Ability to order the food and pay with your credit card or using your crypto wallet
  • Mobile Apps:
  • Ability to select custom ingredients for the selected menu items
  • Ability to choose different menu items and add them to the cart in different sizes
  • A detailed breakdown of the costs and fees (including fiat-based fees to attract more people to move away from fiat and get even better deals)
  • Ability to order the food and pay with your credit card or using your crypto wallet
  • Restaurants onboarding in the target areas
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity

Acceptance Criteria:

  • At this stage, we should already have a complete product
  • We still may need some performance/scalability tunings and bug fixes. But the main flow should work as expected.

Outputs and Evidence to validate the acceptance criteria:

  • Users should be able to search the list of restaurants, navigate their menu, add items they like to the cart, and pay via crypto or fiat.
  • Every order should execute a smart contract and trigger a transaction on the Cardano blockchain.
  • Restaurants receive notifications of the orders via their app and update the order status.
  • Customer support members monitor the order status and help deal with unexpected situations.

Costs: 56,250 ADA or 11.25% of the Grant Amount

Milestone 8: Accounting, statistics, and testing - Final Acceptance Milestone

Duration: 4 weeks (1 month)

Tasks:

  • Bug fixing
  • Performance and scalability tunings
  • Minor improvements when required
  • Accounting dashboard in the admin panel
  • Publicly available statistics dashboard
  • Covering of the main flow and API with automatic tests if the time left
  • Restaurants onboarding in the target areas
  • Project Management:
  • Tasks management
  • Feedback gathering
  • Reporting to the community
  • Community engagement and publicity
  • Launch and a marketing campaign

Acceptance Criteria:

  • Fully functioning and stable product
  • Publicly available statistics (dashboard with different kinds of charts)
  • The marketing campaign in the target areas

Outputs and Evidence to validate the acceptance criteria:

  • The described solution should be stable and don't have any performance issues. Anyone can start using it in real life.
  • Anyone should be able to access the dashboard showing current metrics and the performance of the system at metrics.hungryhaste.com.
  • Demo of the marketing campaign: YouTube advertising, social media ads, marketing brochures (the method still works when you target specific areas as we are going to)

Costs: 56,250 ADA (development) + 50,000 ADA (marketing and launch) = 106,250 ADA or 21.25% of the Grant Amount

Please describe the deliverables, outputs and intended outcomes of each milestone.

Milestone 1: Working environment and infrastructure set up

Deliverables:

  • "Hello, world" versions of every app should be automatically uploaded to the test environment daily and to the staging environment weekly, including to the Android and iOS app stores.
  • Legal documentation is ready.
  • The utility token is minted, and the whitepaper is ready.
  • Communication through social media, online channels, and the Scrum dashboard in GitHub is up and running.

Metrics:

  • "Hello, world" for every app is ready
  • Daily updates on our online channels and social media

Milestone 2: Restaurants onboarding process development

Deliverables:

  • At this point, we should be able to add new restaurants into the system via the API and our Admin Panel.
  • Restaurants should be able to edit their own information via the mobile app.
  • Restaurants can receive the payments in fiat and crypto (the infrastructure is in place, but no functionality in the apps yet)

Milestone 3: Create order functionality

Deliverables:

  • We should be able to create new orders via API.
  • The payment should be sent to the restaurant via fiat or crypto.
  • Every payment, including fiat payments, should trigger crypto transactions on the blockchain (but no smart contract at this stage, just simple transactions).
  • At this point, we should already have at least 30 restaurants in the system, and the paperwork should be signed.

Milestone 4: Customer Apps: login, sign-up, and account management

Deliverables:

  • Users should be able to create their account using the web app or via Android / iOS apps
  • Users should be able to manage their account data using any of the apps
  • Users should be able to add their credit cards to the system (no crypto wallets at this stage)
  • At this point, we should already have at least 60 restaurants in the system, and the paperwork should be signed.

Milestone 5: Customer Apps: Payments

Deliverables:

  • There is a possibility to enter the amount in the web app that we want to send via fiat or crypto.
  • There is a possibility to enter the amount in Android and iOS apps that we want to send via fiat or crypto.
  • Every transaction triggers the smart contract.
  • Fees are encoded in the smart contract logic and can't be changed in a centralized way opening the door for governance implementation.
  • At this point, we should already have at least 90 restaurants in the system, and the paperwork should be signed.

Milestone 6: Customer Apps: Search functionality

Deliverables:

  • Users can enter their current location and see the closes restaurants in their area.
  • Users can filter the restaurants by categories of food.
  • Users can click on every restaurant and see detailed information about the restaurant, including its location, contact details, working hours, and the menu.
  • The above functionality should be available on the web and Android and iOS apps.
  • At this point, we should already have at least 120 restaurants in the system, and the paperwork should be signed.

Milestone 7: Customer Apps: Place an Order and Cart functionality

Deliverables:

  • At this stage, we should already have a complete product
  • We still may need some performance/scalability tunings and bug fixes. But the main flow should work as expected.
  • At this point, we should already have at least 150 restaurants in the system, and the paperwork should be signed.

Milestone 8: Accounting, statistics, and testing

Deliverables:

  • Fully functioning and stable product
  • Publicly available statistics (dashboard with different kinds of charts)
  • At this point, we should already have at least 180 restaurants in the system, and the paperwork should be signed.
  • Marketing campaign: we will target one specific area

Please provide a detailed budget breakdown of the proposed work and resources.

Please look at the spreadsheet file here. And you can find a detailed breakdown for every milestone below:

Milestone 1

Milestone 2

Milestone 3

Milestone 4

Milestone 5

Milestone 6

Milestone 7

Milestone 8

Who is in the project team and what are their roles?

Please meet our team!

We recorded a short intro video here: Our Team Video Intro!

We are Dev Team Inc, a software development agency with expertise in building web and mobile apps and everything that goes hand in hand: cloud infrastructure, database management, big data and data analysis, UI/UX design, and business analysis. One of our priorities at the moment is to move into Web3 and DApps, and many of our engineers are fans of the Cardano platform. We also have our Plutus school and our pool that we plan to use to finance our school, but it's a work in progress at the moment and has yet to be finished.

Our website: <https://www.devteam.inc/>

Our pool: <https://cardano.devteam.inc/>

Our members who will be participating in the project:

1.Dima Bezzubenkov

Role: Product Manager

Responsibilities:

  • Requirements gathering and features prioritization
  • Restaurants and drivers onboarding
  • Customer feedback and research
  • Budget management
  • Marketing and publicity
  • Community reporting
  • Teams interaction (development and marketing)
  • Software development, if required

LinkedIn: <https://www.linkedin.com/in/dimabezzubenkov>

Twitter: <https://twitter.com/dimabezzubenkov>

2. Denis Gvozd

Role: Solution Architect

Responsibilities:

  • Core architecture decisions
  • DevOps
  • SecOps
  • Continues Integration and Delivery
  • Monitoring, Logging, Scalability
  • Code review and analysis
  • Software development, if required

LinkedIn: <https://www.linkedin.com/in/gvozddenis/>

3. Andrei Pakliak

Role: Project Manager

Responsibilities:

  • Daily project and team management
  • Scrum master: developing project scopes and objectives
  • Project progress monitoring and meeting deadlines
  • Ensure the final quality of the product
  • Risk management and assessment
  • Create and maintain comprehensive project documentation
  • Software development, if required

LinkedIn: <https://www.linkedin.com/in/andreypoklyak/>

4. Egor Garkavy

Role: Team Lead and Senior Full Stack Engineer

Responsibilities:

  • API and backend development
  • Authentication process development
  • Angular-based web app development
  • Plutus smart contracts development and deployment
  • Pull requests review
  • Bugfixing, performance, and scalability tunings
  • Helping the rest of the team when needed

LinkedIn: <https://www.linkedin.com/in/egor-garkavy-1baa66125/>

5. Nikita Hripach / Andrei Mikhailovski

Role: Mid Full Stack Engineer

Responsibilities:

  • API and backend development
  • Angular-based web app development
  • Plutus smart contracts development and deployment
  • Pull requests review
  • Bugfixing, performance, and scalability tunings

LinkedIn:

Nikita: <https://www.linkedin.com/in/nikita-hripach/>

Andrei: <https://www.linkedin.com/in/andrew-m-76986820a/>

6. Aktan Rysaliev / Alexey Kulba

Role: Mid React Native Engineer

Responsibilities:

  • Mobile apps development using React Native
  • Wallets integration with mobile devices
  • Pull requests review
  • Bugfixing, performance, and scalability tunings
  • Helping the rest of the team when needed

LinkedIn:

Aktan: <https://www.linkedin.com/in/aktan-rysaliev-4bb770201/>

Alexey: <https://www.linkedin.com/in/aliakseikulba/>

7. Andrei Astapenka

Role: Manual and Automation QA Person

Responsibilities:

  • Manual testing of the web app and mobile apps
  • Creating test cases and test plans
  • Bug reporting
  • API autotests with PostMan
  • UI autotests with Selenium

LinkedIn: <https://www.linkedin.com/in/andrei-astapenka-25607224b/>

8. Suhrob Abdurakhmanov

Role: Senior UI / UX Designer

Responsibilities:

  • UX Research and competitive analysis
  • User personas and user flows identification.
  • Low-level and high-level wireframing
  • Prototype creation
  • UI design based on the prototype

LinkedIn: <https://www.linkedin.com/in/suhrob-abdurahmanov/>

9. Andrei Stanislavchik

Role: Customer Support and Community Manager

Responsibilities:

  • User feedback and interactions
  • Restaurants and drives feedback and support
  • Community engagement in online channels
  • Social media management
  • Handling complaints and improving the overall customer experience

LinkedIn: <https://www.linkedin.com/in/andrey-stanislavchik-060644218/>

10. Yelena Elbaum

Role: Accountant and Legal Advisor

Responsibilities:

  • Set up a legal entity
  • Bookkeeping
  • Yearly and quarterly filings
  • Crypto accounting and bookkeeping advisory

LinkedIn: <https://www.linkedin.com/in/yelena-elbaum-cpa-ctc-150a8a51/>

How does the cost of the project represent value for money for the Cardano ecosystem?

While we understand that it is a high costs proposal (500,000 ADA), we also believe it is an easy-to-sell idea for the masses (20% permanent discount on every order for anyone). Return on the investment for this proposal will be disproportionally justified even if we can get only 1% of the DoorDash audience. 1% of the DoorDash audience translates to:

  • 320k transactions on Cardano per month, even when users are using fiat.
  • Our audience can be people unfamiliar with crypto yet who can be intrigued by additional benefits available only for Cardano users.
  • If we can convert at least 30% of that audience to use the Cardano platform directly and pay in ADA or our native token, we will have additional 100k monthly users on the Cardano platform.
  • It's a real-world example of how the elimination of the middlemen with the help of decentralization can benefit all participants of the system. But for that idea to work, we must build on a truly decentralized platform - Cardano. It's a showcase for VCs why true decentralization matters and why they need to pay more attention to Cardano.

A detailed breakdown of the costs for every milestone can be found in the Budget Breakdown document in the links section. It is based on the average salaries of software engineers in Belarus, Ukraine, and Poland:

  • $4,000 a month for a Senior Engineer
  • $2,500 a month for a Mid Engineer
  • $1,700 a month for a Manual + Automation QA Person (we need only 20 hours a week of QA for this project)
  • $3,350 a month for a Senior UI / UX Designer (we need only 20 hours a week for this project)
close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00