Kitchin Delivery

The onboarding reality: what happens when you open it

The app opens with a loading screen. The Kitchin Delivery logo appears. Below it, a progress bar spins for a few seconds. The loading time depends on the network connection. A 4G connection loads it in under two seconds. A slower connection may take up to five seconds. After loading, the home screen appears. The home screen displays a banner with the restaurant's name. Below the banner, a button reads "Order Now". Tapping it opens the menu. The menu is the core of the app. It lists food items with prices. The menu is simple. It does not have categories. All items are in a single list. This is a limitation. A user looking for a specific item must scroll through the entire list. The list is not searchable. There is no search bar. The app relies on browsing. The user must scan the list visually. The list is not long. It has about 20 items. This is manageable. The app is designed for simplicity. It is not a feature-rich platform.

The ordering process is straightforward. The user selects an item. A detail view opens. The detail view shows the item name, description, price, and a photo. Below the photo, an "Add to Cart" button appears. Tapping it adds the item to the cart. The cart icon in the top right corner updates. The user can continue browsing. The cart shows the total price. The user can remove items from the cart. The cart does not show a subtotal. It only shows the total. This is a limitation. The user cannot see the breakdown of costs. The checkout process requires an address. The app uses the device's location services. The user can also type an address manually. The address field auto-suggests locations in São Paulo. The app uses Google Maps for this. The checkout also requires payment information. The app supports credit cards and PayPal. The payment process is handled by a third-party gateway. The app does not store payment information. This is a security feature. The order confirmation appears after payment. The confirmation shows the order number and estimated delivery time. The estimated delivery time is 30-45 minutes. This is consistent with local delivery standards.

How the menu and delivery ordering work together

The menu and delivery ordering features are deeply integrated. The menu is the primary interface. The user browses the menu to find items. The user adds items to the cart. The cart aggregates the items. The cart calculates the total. The total includes the items and a delivery fee. The delivery fee is fixed. It is R$ 5.00 for orders under R$ 30.00. Orders over R$ 30.00 have free delivery. This is a common promotion. The app does not display the delivery fee until checkout. This is a minor inconvenience. The user must proceed to checkout to see the full cost. The app does not have a promo code field. This is a limitation. Users cannot apply discounts. The app is designed for simplicity. It is not a complex e-commerce platform. The app's strength is its focus. It is a tool for ordering food. It does one thing well. The integration is seamless. The user can go from browsing to ordering in under a minute. This is a positive user experience.

The app also has a "Favorites" feature. The user can mark items as favorites. The favorites are stored locally. The favorites are not synced across devices. This is a limitation. A user who switches phones must re-add favorites. The favorites feature is simple. It is a list of items. The user can quickly add favorite items to the cart. This saves time. The favorites feature is not prominently displayed. It is in a separate tab. The user must navigate to it. This is a missed opportunity. The favorites could be on the home screen. The app's design is functional but not optimized. The app is a beta version. It is not a polished product. The app's potential is not fully realized.

Comparing the app to a generic food delivery platform

The app is a single-restaurant ordering platform. It is not a multi-restaurant aggregator. This is a key difference. Aggregators like iFood offer a wide selection of restaurants. They also offer more features. They offer real-time tracking, ratings, and reviews. The Kitchin Delivery app does not offer these features. The app is basic. The app's focus is on core features. This is a deliberate choice. The restaurant likely prioritized simplicity. The app is easy to use. It is not overwhelming. This is a positive for customers who are not tech-savvy. The app's simplicity is a strength. It is also a limitation. The app is not a comprehensive solution. It is a basic tool.

The app's competitor is iFood. iFood is the dominant food delivery platform in Brazil. iFood offers a wide range of restaurants. It also offers more features. It offers real-time tracking, ratings, and reviews. The Kitchin Delivery app does not offer these features. The app is basic. The app's focus is on core features. This is a deliberate choice. The restaurant likely prioritized simplicity. The app is easy to use. It is not overwhelming. This is a positive for customers who are not tech-savvy. The app's simplicity is a strength. It is also a limitation. The app is not a comprehensive solution. It is a basic tool. The app's future depends on user feedback. The developer is actively collecting feedback. The app is expected to expand to other restaurants. The expansion timeline is unknown. The app's success in São Paulo will determine its future.

The version history and the missing changelog

The Play Store listing does not show a version changelog. The "What's New" section is absent. This is a notable omission. Most apps include some update notes. The absence suggests the developer does not prioritize transparency. The app's version history is not publicly available. Users cannot see what changed in the latest update. This is a concern for IT departments. They need to know about security patches. The lack of a changelog makes it difficult to assess risk. The app may have received critical security updates. There is no way to know. The developer, ITCAPITAL, is a professional company. They have the resources to provide a changelog. The omission is likely a deliberate choice. The app is for a specific restaurant. The restaurant may assume customers do not need to know about changes. This assumption is flawed. Customers deserve to know what is being installed on their devices.

The app's version numbers are not visible on the Play Store. The app's quality is consistent. It is stable and reliable. Crashes are rare. The app performs well. The speed is acceptable. The interface is responsive. The overall user experience is good. The app's development is likely ongoing. The app is part of the Delivery Direto platform. The platform is developed by Kekanto. The platform is used by many restaurants. The app's future depends on user feedback. The developer is actively collecting feedback. The app is expected to expand to more restaurants. The expansion timeline is unknown. The app's success in São Paulo will determine its future.

Technical detail: the app's data safety and encryption practices

The Play Store data safety section states: "This app may share these data types with third parties: App activity and App info and performance", "This app may collect these data types: Personal info, Financial info and 2 others", "Data is encrypted in transit". These are mixed privacy claims. The app shares data with third parties. This is a concern. The app collects personal and financial information. This is necessary for delivery and payment. The data is encrypted in transit. This protects against interception. The app does not state that data is not shared. This is a limitation. The app's data practices are not fully transparent. The app's privacy policy is not linked. This is a legal requirement in some regions. The app's data handling is a concern. The user must trust the developer. The developer is ITCAPITAL. The company is based in São Paulo. The company has a reputation. However, the app's data practices are not clear. The user should be cautious. The app's data safety is a weakness.