City Gateway: Innovative, Social, and Learning

For the development of the Rietavas digital gateway (project "Rietaviškis"), Flutter (Dart) is the preferred platform over React Native or native iOS/Android development. This preference is driven by the project's specific requirements for long-term stability, strict accessibility standards, and the adoption of a unified architectural pattern.

Why is Flutter Preferred?

• Accessibility and Universal Design: Flutter’s Skia/Impeller rendering engine allows for pixel-perfect UI control, which is essential for achieving the mandatory 100% accessibility pass rate for seniors and individuals with disabilities. It provides deep, uncompromised hooks into native accessibility APIs like iOS VoiceOver and Android TalkBack.

• Predictable Maintenance: Given the requirement for a 5-year maintenance cycle, Flutter offers predictable multi-year stability compared to the often-shifting dependency landscape of other frameworks.

• Architectural Efficiency: By using Flutter as a cross-platform shell, the project avoids the "quadruple implementation" problem (independently coding for iOS, Android, Web Touch, and Web Desktop), which typically leads to inconsistent business logic and fourfold labour costs.

• Unified Business Logic: The application leverages a Backend for Frontend (BFF) architecture, which centralises complex business rules (like credit matrices and eligibility) on the server side. Flutter acts as a performant client for this "single source of truth," accelerating Time to Market (TTM) to approximately 1–1.5 weeks for functional changes.

• Edge AI Integration: Flutter is well-suited for deploying Edge AI runtimes, such as Google AI Edge (LiteRT), which allow sensitive user profiling data to remain strictly on-device to satisfy GDPR Article 25.

Expert Comments and Suggestions:

• Avoid Native Silos: While native iOS/Android development offers high performance, the sources caution that it fragments business logic and complicates the quality assurance process, making it difficult to guarantee identical behaviour across platforms.

• Centralise Testing: Rather than maintaining thousands of disparate client-side tests, you should implement a centralised server-side integration testing suite. This approach has been shown to reduce critical production incidents by 60%.

• Enforce Universal Design Constraints: To prevent UI breaks under extreme conditions, suggest capping the dynamic text scale factor at 200% and ensuring all interactive elements have a minimum touch-target size of 48×48 logical pixels.

• Prioritise Offline-First Verification: For the Proof-of-Participation module, use an offline-first cryptographic pipeline (such as Ed25519 asymmetric verification). This ensures a verification velocity of < 30 seconds, even in areas with poor municipal Wi-Fi or cellular coverage.

• Adopt Standardised Protocols: Ensure the mobile agent uses the Model Context Protocol (MCP) and Agent-to-Agent (A2A) v1.2 for secure discovery and task delegation to local service providers