Èze Creperie

The onboarding reality: what happens when you open the app

The app opens with a loading screen. The Èze Crêperie 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 the restaurant's name and a photo of a crepe. Below the photo, a button reads "Order Now". Tapping it opens the menu. The menu is the core of the app. It lists sweet crepes, savory crepes, and omelets. Each item has a name, a description, and a price. The prices are in Brazilian Reais (R$). The menu 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, a "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 Florianópolis. 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 crepes. 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.

Real-world performance: what works and what doesn't

The app performs well in Florianópolis. The user base is small but active. The app is stable. Crashes are rare. The app loads quickly. The menu images load fast. The images are optimized for mobile. The ordering process is smooth. The payment gateway works reliably. The app does not have ads. This is a positive. The app is completely free. There are no in-app purchases. The developer may introduce monetization later. For now, the app is a community project. The focus is on building a user base. 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 Florianópolis will determine its future.

However, there are limitations. The app is only available in Portuguese. This is a restriction. Users who do not speak Portuguese cannot use the app. The app also lacks multi-language support. The app does not have a tutorial. New users must explore on their own. The app also lacks a feedback mechanism. Users cannot report bugs or suggest features. This is a missed opportunity. The developer email is listed on the Play Store. However, this is not user-friendly. The app should have an in-app feedback form. The app also has no analytics. The developer cannot track user behavior. This makes it difficult to improve the app. The app's data safety is commendable. It does not collect or share data. However, data is not encrypted. This is a privacy concern. The app also does not have a privacy policy link. This is a legal requirement in some regions. The app is still in beta. These issues are expected. They will likely be addressed in future updates.

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. They also offer more features. They offer real-time tracking, ratings, and reviews. The Èze Creperie 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 Èze Creperie 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 Florianópolis 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.