About Nakaza Sushi
Placing an Order: The Core Workflow
Open the app. The first screen shows the restaurant's logo and a simple interface. No login required for browsing. Tap the menu button. A list of categories appears: sushi, sashimi, temaki, hot dishes, and the Nakaza Poke. Select an item. A description and price pop up. Tap "Add to cart." The cart icon updates instantly. Repeat for multiple items. Review the cart. Each item shows quantity and price. Adjust quantities or remove items with a tap. Proceed to checkout. Enter delivery address. The app validates the address against the restaurant's delivery zone. Choose payment method: credit card, debit card, or cash on delivery. Confirm the order. A confirmation screen appears with an order number and estimated delivery time. The app sends a push notification when the order is accepted. Another notification when the driver is on the way. A final notification when the order arrives. That is the complete workflow. It takes about 90 seconds from opening the app to placing an order, assuming the user knows what they want.
This workflow is streamlined for speed. The developer, Delivery Direto by Kekanto, has built a white-label platform for restaurants. Nakaza Sushi is one of many brands using this system. The app does not have a search bar or filters. It relies on the restaurant's own menu structure. This simplicity reduces friction for repeat customers. They know the menu. They just want to order quickly. The app delivers on that promise. No unnecessary steps. No account creation required for first-time users. Just tap, select, and pay.
Nakaza Sushi vs. iFood: A Comparison of Delivery Approaches
iFood dominates food delivery in Brazil. It aggregates thousands of restaurants. Nakaza Sushi's app does the opposite. It focuses on one restaurant. This difference shapes the user experience. On iFood, a user searches for sushi, compares options, reads reviews, and chooses. On Nakaza Sushi, the user already knows the restaurant. They open the app to order directly. No comparison. No distraction. The app's interface is minimal. iFood's interface is cluttered with promotions, ads, and multiple restaurants. Nakaza Sushi's app shows only the menu and the cart. This direct approach benefits the restaurant. It avoids iFood's commission fees, which can reach 20-30% per order. The restaurant saves money. The customer may get lower prices or better service.
However, the app lacks iFood's features. No real-time driver tracking on a map. No chat support. No rating system for individual dishes. The app only provides basic order status notifications. iFood offers a richer experience. But Nakaza Sushi's app is not trying to compete with iFood. It is a supplementary channel. The restaurant also lists on iFood, as confirmed by the Revista Sabores do Sul article. Customers can choose. Those who want convenience and lower fees use the app. Those who want variety use iFood. The app's simplicity is its strength. It does one thing well: take orders for Nakaza Sushi.
What the Changelog Does Not Reveal
The Google Play listing has no published changelog. The "What's New" section is blank. This is common for Delivery Direto apps. The version history shows version 2.19.16, last updated August 25, 2025. The previous version, 2.19.6, was released in April 2023 for similar apps. The gap suggests minor updates. The APK size is 5.44 MB, indicating a lightweight app. No new features are announced. No bug fixes are listed. The developer does not communicate changes to users. This lack of transparency is a pattern. Other Delivery Direto apps, like Nakato Sushi Delivery, also have blank changelogs. The only hints come from third-party sites. APKPure notes "Minor bug fixes and improvements" for Nakato Sushi Delivery, but that is a generic description. It likely applies to Nakaza Sushi as well.
The absence of a changelog matters for trust. Users have no way of knowing what changed. Did the app fix a payment bug? Did it improve order reliability? Did it add support for new Android versions? The developer does not say. This silence is acceptable for a simple ordering app. The app works. It does not need constant updates. But it leaves users guessing. A simple changelog would build confidence. Instead, the developer relies on the app's stability. The app has not crashed or shown major issues in the research. That is a positive sign.
The Nakaza Poke: A Customization Feature That Stands Out
The Nakaza Poke is not a standard sushi item. It is a build-your-own bowl. Customers choose a base, protein, vegetables, and sauce. The twist: fruits are included as an option. Pineapple, mango, and even strawberries can go into the poke bowl. This is unusual for a sushi restaurant. The app lists this as a separate category. Users can select ingredients one by one. The price adjusts based on choices. This feature is not available on iFood for this restaurant. It is exclusive to the app. The app's menu structure supports this customization. Each ingredient is a separate item with a price. The cart calculates the total dynamically. This is a niche use-case. It caters to adventurous eaters. It also shows the restaurant's creativity. The owner, Suellyn Monteiro, introduced this in 2024, according to G1 Globo. The app reflects that innovation. A customer ordering a Nakaza Poke experiences the app's flexibility. The workflow is similar to ordering sushi but with more steps. Select base, select protein, select vegetables, select fruits, select sauce. The app handles the complexity. The final price is displayed clearly. This feature sets Nakaza Sushi apart from competitors.
Get File
App Specifications
| Latest Version | 2.19.16 |
| Uploaded by | Delivery Direto by Kekanto |
| Requires Android | Android 5.0+ |
| Category | Food & Drink |
| Content Rating | Rated for 3+ |
Technical Details
| Package Name | com.delivery.nakazaSushi |
| Languages | English |
| Architecture | arm64-v8a |
| Signature | 65492be23a4dc647b0932a2fd536959c72f279d66462e377e802eb82ba0e9c87 |
Security & Additional Info
| Scan Result | Secure |
| Package Name | com.delivery.nakazaSushi |
| SHA‑256 | 65492be23a4dc647b0932a2fd536959c72f279d66462e377e802eb82ba0e9c87 |
| SHA‑1 | 8d9d6f02b1f8bd094ecc0fd2fc0a1ba037a8d95a |
| App Permissions | 0 |