A low-code platform for mobile applications

Context

At FFAUG LTD, I combined a founder’s responsibilities with hands-on software and systems work. A central part of that experience was designing and developing a low-code mobile application platform using Android, Kotlin, Java and Flutter.

The scope connected the application experience with the services and infrastructure behind it. It included Firebase integration, delivery automation, cloud hosting and server operations.

My responsibility

As Co-Founder & Lead Developer, I worked across application development and system architecture. I designed and developed the mobile platform, integrated applications with Firebase for real-time data and authentication, and implemented analytics and advertising systems within mobile applications.

The same role included web development with Angular and Vue.js, cloud architecture, CI/CD and automation. This breadth meant working through the relationship between product features and the systems needed to support them.

Engineering approach

The mobile work used Android technologies alongside Flutter. Firebase provided application services for real-time data handling and user authentication. The web work included cross-platform compatibility and responsive interfaces.

The surrounding infrastructure used AWS, GCP, Netlify and Cloudflare. I developed delivery pipelines with GitHub Actions and Ansible and wrote automation for data processing and deployment workflows.

I also managed Linux and Windows server environments, worked on network configuration and automated recurring system tasks. Cloud monitoring supported performance analysis and operational investigation.

Complexity and trade-offs

A mobile platform has to account for application behavior, service integration and the environments in which it runs. Native Android and cross-platform development offer different ways to organise that work, while shared application services create dependencies that need to remain understandable.

Low-code development adds another architectural concern: deciding which behavior can be shared and which needs to remain configurable. My work on the platform sat alongside the delivery, infrastructure and operations needed to make those applications usable.

Integrating authentication, real-time data, analytics and advertising also brings several service boundaries into the application. The engineering work includes coordinating those responsibilities rather than treating each integration as an isolated feature.

What this work brought together

My FFAUG experience brought mobile application development, platform design, cloud infrastructure and operational automation into the same role. It is a substantial part of how I developed an engineering approach that follows a feature from its interface through to deployment and operation.

Sources & further reading

• Professional profile