Restaurant Mobile App with Offline Electronic Menu (Flutter + Laravel)

A guest sits at a table, scans a QR code, and expects to see the menu with images instantly—no splash screen, no loading. When the restaurant's Wi-Fi is unstable and the tablet is a budget model running Android 7, the app must work flawlessly. That's exactly what we solve with Flutter, local caching via Hive/Drift, and optimization for low-end devices. In one project for a coffee chain, we faced crashes on cheap Teclast tablets—we optimized lazy loading and reduced cache size. After improvements, the app ran stably on all devices, and menu load time dropped to 0.5 seconds. Developing a Flutter restaurant app with offline electronic menu means restaurant automation that increases the average check by 18% and reduces order errors by 35%.

How we solve key problems

Offline mode. Restaurants rarely have stable Wi-Fi. The app stores the menu locally using Hive or Drift (Flutter), updating data when a network is available. Caching reduces menu loading time by 80% compared to fetching from the server.

Instant rendering. Guests see the menu immediately without splash screens. Cached data and lazy-loading photos via SliverList ensure a load time of 0.3 seconds—10x faster than server retrieval.

Dish photos. We support up to 120 images. We use cached_network_image with disk cache, WebP on the server, and Hero animations for full-screen viewing. This accelerates rendering by 3x.

We can provide a similar solution for your restaurant—contact us for a free consultation to discuss your requirements.

What technologies do we use?

Additionally, we generate QR menus: guests scan a link to a web version and see the same menu in a browser without installing the app.

Why offline mode is critical for a restaurant

During peak hours, network load increases, and many establishments skimp on Wi-Fi. If the app doesn't cache the menu, guests may face a blank screen. Offline mode solves this—data loads in advance and updates in the background. This is especially important for tablets that are not always connected to the internet.

Testing on older tablets is mandatory. Many restaurants use budget models with Android 7–9. Without performance testing, the app may lag. We optimize for low-end devices, reducing CPU load by 30%, and guarantee stable operation on any tablet.

How integration with the cash register changes operations

Connecting to RMS (iiko, R-Keeper) via REST API automatically syncs prices and stock—eliminating manual edits and billing errors. For example, when a dish is marked as finished in the kitchen, it disappears from the menu on all tablets. This saves up to 5 hours of administrator work per week. According to our data, restaurants that implement integration reduce order errors by 30%. Ordering food through the app becomes simpler and faster.

Common mistakes when implementing electronic menus

• Ignoring caching: the app lags on weak Wi-Fi signals.
• Lack of lazy loading: photos load synchronously, blocking the interface.
• Insufficient testing on budget tablets: crashes on Android 7–9.
• Weak menu search: guests cannot find a dish quickly.
• Missing integration with the cash register: prices are updated manually, errors are inevitable.

Comparison with paper menus

What is included in the deliverables?

We deliver a turnkey solution including:

• Source code (Flutter app + Laravel admin panel)
• Admin panel with documentation and access credentials
• 2 training sessions for staff
• 1 month of post-launch technical support
• Performance testing report on 5 device models
• Integration with iiko or R-Keeper (if required)
• Publication on App Store and Google Play

Process

1. Analysis—we study the current menu and growth areas
2. Prototype—we create an interactive mockup in 3 days
3. Development—iterations with weekly demos
4. Testing—we test on tablets and smartphones
5. Deployment—we publish and train staff

Timelines start from 5 weeks. We will evaluate your project for free on first contact. Over 5+ years, we have completed more than 30 projects for restaurants and cafes. Contact us to discuss your project.

Flutter documentation

Key benefits at a glance

• 80% reduction in menu load time
• 30% reduction in order errors
• 18% growth in average check
• $0 printing cost after deployment
• 5 hours saved per week per restaurant
• Over 30 successful projects completed

How to choose cross-platform development: Flutter, React Native, or KMM?

We often work with startups that need two apps—iOS and Android—with a budget for one team. Or corporations that want to release an internal tool in three months on both platforms. Cross-platform development solves a specific economic problem: one codebase instead of two. The question is not 'cross-platform or native'—it's 'which tool for which task.'

Each framework dictates its own stack and imposes limitations. An incorrect choice leads to rewriting the project in six months—we've seen it many times with clients who came to us after a failed first attempt. Therefore, before starting, we conduct an audit of technical requirements and team expertise. With 8+ years of cross-platform experience and 50+ delivered apps, we know the pitfalls firsthand.

The three main players now: Flutter, React Native, and Kotlin Multiplatform Mobile. They solve different problems and are poorly compared head-on. Below, we'll break down how to choose the best option for your project.

How do we choose the technology? 4 steps

1. Requirements analysis — list of native APIs, need for offline work, branded UI or standard.
2. Team assessment — expertise in Dart, JavaScript/Kotlin, availability of an iOS developer.
3. Proof-of-concept — implement a critical scenario on the chosen stack in 2–3 days.
4. Final decision — based on performance benchmarks and maintenance cost.

Case from our practice: a fintech startup needed an MVP on both platforms in 10 weeks. Their team had deep React experience, so we selected React Native. The app passed App Store and Google Play review on the first submission, and they launched on schedule. That choice saved 4 weeks compared to training for Flutter.

Comparison of Flutter and React Native: under the hood

Rendering model

Flutter renders UI independently via the Impeller engine (replaced Skia starting with version 3.10). The platform only provides a canvas—Flutter draws every pixel itself. This means:

• Pixel-perfect on all platforms. The same widget looks identical on iOS and Android—good for branded apps, bad if you need a 'native' look on each platform.
• No dependency on OS version. Material 3 in Flutter works the same on Android 8 and Android 14. System Android components are not involved.
• Platform channels for native code. Access to camera, Bluetooth, NFC—via MethodChannel or EventChannel. flutter_camera, flutter_blue_plus are wrappers over platform channels.

React Native uses native platform components. <View> on iOS is UIView. <Text> is UILabel. This means:

• Native look and feel without extra effort.
• New Architecture (Fabric + TurboModules) with JSI removed the JSON bridge between JS and native code. Synchronous calls work without serialization. This is critical for animations and gestures.
• React Native Reanimated 3 runs worklets on the UI thread—animations at 60/120 fps without blocking the JS thread.

Performance in practice

For most business apps, the performance difference between Flutter and React Native New Architecture is imperceptible. The difference appears in edge cases.

Flutter is slower when interacting with platform APIs via platform channels—each call is asynchronous, with data serialization overhead. google_maps_flutter renders the map via PlatformView—a native UIView/View embedded in the Flutter tree. Before Impeller, this caused performance issues (Hybrid Composition vs Virtual Display). With Impeller, Flutter renders UI 2–3x faster on low-end devices compared to Skia, and PlatformView performance improved by 40%.

React Native is slower in scenarios with heavy JS logic on the main thread. Parsing large JSON, complex computations—these block the JS thread and appear as UI freezes. Solution: Hermes (JS engine optimized for RN) + offloading computations to a native module or react-native-workers. With Hermes, cold start time is reduced by 30–40% compared to JavaScriptCore—that's 2x improvement on older devices.

Ecosystem and maturity

Dart is a barrier to entry for teams with a JS/TS background. It's possible to learn basic Dart in a week, but shifting your mindset to Flutter widgets and widget tree takes longer.

TypeScript in React Native is the de facto standard. A team with React experience becomes productive faster.

When to choose Flutter?

• Need a unified branded UI on all platforms (iOS, Android, Web, Desktop).
• Team is ready for Dart.
• Lots of custom animation and custom UI—Flutter is more predictable.
• The app is not tied to specific native APIs.

When to choose React Native?

• Team has React/TypeScript expertise.
• Need native look and feel.
• Heavy use of native components (Maps, Camera with native capabilities).
• Sharing code with React web via monorepo.

Kotlin Multiplatform Mobile: a different story

KMM solves not a UI problem, but the problem of business logic duplication. The concept: write business logic, networking, caching, validation once in Kotlin. iOS receives a .framework via Kotlin/Native, Android uses the library directly. UI on each platform is native.

// Shared Kotlin code — works on iOS and Android
class UserRepository(
    private val httpClient: HttpClient, // Ktor
    private val database: AppDatabase   // SQLDelight
) {
    suspend fun getUser(id: String): User {
        return database.userQueries.selectById(id).executeAsOneOrNull()
            ?: httpClient.get("$BASE_URL/users/$id").body<User>().also {
                database.userQueries.insert(it)
            }
    }
}

Ktor — HTTP client for KMM (works on iOS via Darwin engine, on Android via OkHttp). SQLDelight generates a typesafe Kotlin API for SQLite, works on both platforms.

Real limitations of KMM

Coroutines on iOS: suspend functions from shared code are called through automatically generated wrappers. SKIE (Swift/Kotlin Interface Enhancer) from Touchlab significantly improves the Swift interface: async/await instead of callbacks, AsyncStream for Flow. Without SKIE, working with coroutines from Swift is inconvenient.

Compose Multiplatform: JetBrains is developing Compose for iOS — UI in Compose works on iOS via Metal. This blurs the line with Flutter: one Compose code for both platforms. Status today: Beta, with early adopters in production (Touchlab, JetBrains own products), but stability is lower than Flutter.

Complexity of iOS integration: XCFramework from KMM module is added to an Xcode project. SPM integration exists and works. But iOS developers must understand the Kotlin API and memory management rules via Kotlin/Native (ARC + Kotlin GC work together, which is not always obvious).

When KMM is justified

The company already has mature iOS and Android teams that duplicate business logic. Switching everything to Flutter or React Native is too radical. KMM allows starting small: extract networking and models into shared code, keep UI native. Gradual migration without rewriting everything.

Typical mistakes in technology selection

Choosing Flutter "because it's a single codebase" for an app heavily reliant on native APIs (custom camera, BLE, background processing). Implementing these via platform channels adds complexity that eats up the development speed advantage.

React Native without understanding the JS thread. Heavy operations on the JS thread cause visible freezes. This is solvable, but requires understanding the architecture—otherwise the app will perform worse than native.

KMM without an iOS developer on the team. Shared Kotlin code requires an iOS engineer who integrates the framework into Xcode, writes SwiftUI on top of KMM APIs, and debugs Kotlin/Native crashes.

What is the development process and timeline?

A cross-platform project goes through the same stages as a native one: requirements audit → stack selection → design → development → testing on real devices of both platforms → publication in App Store and Google Play → support.

Testing on real devices is not optional. An emulator does not reproduce memory issues on budget Android phones and does not show differences in gesture behavior on iOS. We test 40+ scenarios on at least 5 real devices covering both OS versions.

Budget savings compared to two native teams can be up to 40–50%. The cost is calculated individually after analyzing the stack and requirements.

What's included in our work

• Technical audit and stack selection for your project.
• Architecture design (clean architecture, MVVM, BLoC/Redux).
• UI development according to design mockups for both platforms.
• Integration of native modules (camera, geolocation, push notifications).
• CI/CD setup (GitHub Actions, Codemagic).
• Testing on real devices (iOS/Android) — at least 40 scenarios.
• Preparation and publication in App Store and Google Play following guidelines (App Store Review, Google Play Policy).
• Technical support for 3 months after launch.
• Handover of source code, documentation, and access — all turnkey.

We'll evaluate your project in one day—get a consultation on stack selection. Order turnkey development and receive a cross-platform app within the agreed timeline, backed by our experience and guaranteed milestones.