Media and local news
MD Voice Mobile App
A Flutter Arabic news mobile app integrated with the MD Voice platform, featuring RTL article feeds, categories, live-news cues, authentication flows, deep links, Firebase, and App Store/Google Play release support.
Services involved
Challenge
The MD Voice mobile experience needed to bring the platform's Arabic news coverage into a polished app that felt natural for RTL readers. The app needed category discovery, article browsing, saved and shared article interactions, notifications and settings, login flows, app links, store-release readiness, and reliable coordination with backend APIs and the public website.
Solution
CloudGoUp supported the mobile app integration using Flutter, Dart, Firebase, REST APIs, OAuth2, iOS Universal Links, Android App Links, Google Analytics, and App Store and Google Play release workflows. The work covered mobile app integration, backend API coordination, deep linking, analytics setup, release support, and deployment preparation so article links could move cleanly between the website, app, and store listings.
Outcomes
- Delivered a mobile-first Arabic RTL news app experience connected to the MD Voice platform
- Supported Google Play and App Store release requirements for the live mobile application
- Integrated deep linking through iOS Universal Links and Android App Links
- Connected authentication, Firebase, analytics, and backend API flows for app-ready news delivery
Features planned
- Arabic RTL mobile app UI
- News feed and article browsing
- Category navigation
- Live and breaking-news cues
- Saved and shared article controls
- Notifications and settings screens
- Email login flow
- Google and Apple sign-in support
- Firebase integration
- iOS Universal Links
- Android App Links
- App Store and Google Play release support
Implementation approach
CloudGoUp treats each case study as a connected system rather than an isolated interface. The planning work covers user journeys, content structure, technical architecture, measurement, performance, and operational handoff so the project can support future growth instead of becoming difficult to maintain after launch.
The same approach can be adapted for new builds, redesigns, audits, migrations, analytics improvements, and staged roadmaps where the business needs progress without losing control of quality or scope.
User journey
The experience should clarify who uses the system, what they need to do first, and which decisions must feel obvious.
Technical structure
Content, data, integrations, admin workflows, analytics, and performance requirements should be planned before interface polish.
Launch readiness
QA, SEO, accessibility, events, redirects, security basics, and operational ownership reduce risk when the project goes live.
Planning questions
What this kind of project needs before implementation
- Which user journey needs to be easiest on the first release?
- What data, integrations, and admin controls are required behind the interface?
- Which analytics events prove that the product is creating useful business activity?
- What should be built now, and what should stay in the roadmap until the first version proves value?