TasteTech was built on Flutter v2.x, a version with no sound null safety and no web build target. That left the codebase exposed to null-reference crashes at runtime and made it impossible to add the same app to a browser. Staying on the old version also blocked newer packages and platform features that had already moved to null-safe, web-capable APIs.
The client needed payments to behave identically on mobile and web, but the conventional payment gateway SDKs they evaluated were not economical and would have required separate, platform-specific integrations to cover Android, iOS, and the new web target.
TasteTech started as a mobile-only application; several of its dependencies and UI assumptions did not translate to the browser. Packages needed web-compatible versions, the layout had to work on large desktop displays rather than just phone screens, and navigation built on mobile patterns broke against the web’s URL-based routing.
The client wanted contactless, automated ordering: a diner should be able to scan a code at a specific table or outlet and land directly in the right store’s menu, on both Android and iOS, without manually searching for the location.
Years of Business
Experience
Happy
Customers
Countries with
Happy Customers
Agile enabled
employees