EatIn App
Through an App, instantly connect starving eaters with home cooks offering their home-made food dishes. Users and cooks can choose between enjoying food at the cook's home, pick their food up or get it delivered.
FullStack & Designer
../Responsabilities..
- Develop a mobile-first UI/UX using React Native, ensuring smooth interactions across devices.
- Create separate dashboards for cooks to manage their meals, track orders, and view reviews, and for eaters to browse meals and track orders.
- Implement dynamic search and filtering for eaters to find meals based on cuisine, location, price, and availability.
- Build an intuitive ordering system with secure checkout, order history, and live order status.
- Create wireframes and prototypes using Figma, to visualize the app’s flow for both cooks and eaters.
- Define user journeys for both cooks and eaters to ensure that their paths through the app are efficient and enjoyable.
- Implement tests for both frontend and backend components, ensuring everything functions as expected.
- Set up a continuous integration and deployment pipeline to ensure automated testing and reliable deployments of new features and updates.
- Integrate Google Maps or another geolocation API for real-time cook discovery, meal delivery tracking, and proximity-based recommendations.
Clients
../Stack...
React Native / React / FeatherJs / Typescript / socketio / Async / JWT Auth / API REST / CRUD / Styled Components / Redux / MongoDB / Google Cloud Platform
Insights
Our first concern was delivering a functional prototype fast; every choice had great weight. Knowing what would fit inside the schedule and having experience let me choose the correct tools for every task.
Manual testing and deployment took time, hence we developed automated workflows using constant integration and delivery (CI/CD). This greatly cut the time spent building, installing, and testing on cellphones by allowing us to perform integration tests effectively and show progress without delay.
Using already-existing systems including Heroku, TestFlight, GitHub Actions, and Device Farm let us avoid starting from scratch with infrastructure building. “Standing on the shoulders of giants” let us concentrate on the central offering rather than reinventing the wheel.
Our design process’s web-based, collaborative character and emphasis on web/app design led me to suggest Figma. Considering colors, themes, user interactions, and performance, I developed a design system that fit quite well in a component library. Better abstraction and efficiency in design were made possible by my developer perspective.
Working on the back-end and both front-end apps allowed me complete control over the user flow—from registration to order creation and content uploads. With every iteration, our custom-made CI/CD pipeline saved a great deal of time.
Thanks to the agile methodology we developed, we were happy with the outcome when we effectively introduced a functional prototype in three to four months.