The idea for Intueat arose when Leo – the founder and CEO – orchestrated an in-home dining experience for his girlfriend. That special evening required dozens of calls and complex planning. Because we’re not all like Leo, Chef Connect exists for the rest of us.
Our first task for Intueat was brainstorming with Leo to determine the desired functionality and rough layout for the application. This process began with pencil sketches and whiteboards and ended with high-resolution design files. These files served as blueprints as we moved into development, where we turned those designs into functional code.
We chose Ruby on Rails for the back-end, React Native for the front-end, and leveraged several third-party APIs, including Google for maps and analytics, Facebook for analytics, Live Chat for chat, and Stripe for payment processing. We kept the software architecture simple, favoring a smart/dumb component model on the front-end and default Rails MVC architecture for the back-end, augmented with Service Objects to keep business logic clean, contained, and flexible.