Dxflix
DXFLIX was one of my \early client projects\ and one of the projects that gave me practical experience building a mobile application around an existing web-based system. The client already had a movie website where content was being managed and stored. Rather than rebuilding the entire platform, the requirement was to create a \dedicated mobile experience\ that could consume the existing movie data and present it in a way that felt natural on a phone. My responsibility was focused on the Flutter application: building the mobile interface, connecting it to the client's existing backend/database infrastructure, retrieving movie information, displaying available content, and making the associated video files accessible to users for streaming or download. This made the project particularly useful as an early engineering experience because the application was not operating in isolation. I had to understand how the existing website stored and exposed its information, how the mobile application could communicate with that system, and how movie metadata and video links should move from the backend into the application. The project was less about creating a complicated new platform and more about \connecting an existing content system to a completely new mobile experience.
Problem and context
From an existing movie website to a mobile experience The client already had a website for managing and presenting movie content. The problem was that the existing experience was primarily designed around the web, while there was a need for users to access the same content through a dedicated mobile application. The requirement was not to create another completely independent movie platform. It was to \extend the existing system into mobile. Movie information already existed in the client's infrastructure. What the application needed to do was consume that information, organize it into a mobile-friendly experience, and connect each movie to the appropriate video resource. That meant the application needed to understand the relationship between the data coming from the backend and what the user actually sees inside the mobile application. A movie record was not useful by itself. The application needed to turn that record into something a user could discover, open, watch, and, where supported, download. This created a simple but important engineering workflow: Backend data → Movie information → Mobile interface → Video resource → User action For me, this was an important early lesson in application development: \the mobile app was only one part of the system. The quality of the experience depended on how well the app communicated with the infrastructure behind it.
Outcome
DXFLIX successfully extended the client's existing movie platform into a \dedicated mobile application. Instead of requiring the client to build an entirely new backend ecosystem, the application worked with the infrastructure that was already available and gave users a more direct way to browse and access movie content from mobile devices. The project also gave me practical experience with an important part of software engineering that is easy to overlook when building personal projects: \integrating with systems that already exist. I had to work with an existing database, existing hosting, existing requirements, and existing content rather than controlling every part of the system myself. That made DXFLIX an important early step in my development as a software engineer.
Technologies: Flutter, Dart, PHP, MySQL, Chromecast SDK