• EatIn App
  • EatIn App Design
  • EatIn App Development

EatIn App

Social application that offers a channel to connect cookers and eaters at their homes.

EatIn App

  • Country

    • US
  • Industry

    • Food
  • Project scope and technology

    • Application Design.
    • Build launch landing page.
    • Build application using React Native (iOS / Android).
    • Build back-end.
    • Payments integration.
    • User auth/authorization.
    • Create design system.
    • CI/CD

"Highest priority: launch as soon as possible."


Like Uber application model, we actually needed to develop two applications, one for eaters and one for cookers.

Real-time communication between applications was essential.

Start from zero. Having just an idea and some napkin sketches.

Small team.

Zero codebase.

No design.

Outcome & Findings

To have a functional prototype as soon as possible was the most important task here. We need to be very clever in each decision we made. Experience is what gives you advantage in these situations, we can choose the right tool for each task, we already know what could work and what couldn't in the time range we had.

Running tests by ourselves, compile and install the application everytime on our smartphones consume a lot of time. We decided to use automated actions cover that area, implementing a continuous integration and delivering was helpful to show progress and running integration test between apps.

"Standing on the shoulders of giants." We opted to use PaaS/SaaS instead to waste time building everything from scratch like: Heroku, TestFlight, Github actions, Device Farm, etc.

I proposed to use figma as out designing tool, because is web based, collaborative and web/app design targeted. With Figma I created our design system that was perfectly translated to our component library with colors, themes, interactions, user flows, fonts, sizes, etc. I consider an advantage designing like a programmer, we tend to abstract the content the way we know will work, considering performance as well.

Collaborating in the back-end services as well as in both applications brings me absolutely autonomy to create entire user flow, from the registration to the creation of an order and upload of content. Having our custom-made CI/CD save us a lot of time on each version iteration.

At the end we launch a functional prototype in 3-4 months of development. We were really happy with the result and the agile process we created.