DEV Community

Cover image for Rebuilding MTA ONE v4: Why I Simplified an App That Already Worked
Cahyanudien Aziz Saputra
Cahyanudien Aziz Saputra

Posted on

Rebuilding MTA ONE v4: Why I Simplified an App That Already Worked

Sometimes, rebuilding an application is not because the old version is broken.

Sometimes, it is because the application has become too complicated.

MTA ONE was already working. Users could watch MTA TV, listen to online radio, read weekly brochures, and access several other features.

But after years of development, I started to realize something:

The application was trying to become too many things at once.

And as a solo developer, maintaining everything with the same quality was becoming harder.

That is why I decided to rebuild MTA ONE version 4.

Not by adding more features.

But by simplifying it.

The Problem Was Not the Code

When an application grows, adding features feels like progress.

A new menu here.

A new category there.

Another useful feature for users.

At some point, the application becomes larger, but not necessarily better.

Some features require continuous maintenance:

  • Updating content
  • Managing data
  • Fixing edge cases
  • Handling user reports
  • Testing across different devices

These tasks are manageable when there is a dedicated team.

But I am building and maintaining multiple applications by myself.

So I needed to make a decision.

Should I keep expanding MTA ONE into an application with many unrelated features?

Or should I return to the core purpose?

I chose the second option.

From Flutter to Kotlin Native

One of the biggest changes in MTA ONE v4 is the technology behind it.

The previous version was built with Flutter.

For version 4, I rebuilt it using Kotlin Native with Jetpack Compose.

The migration started around August 19, 2026, and the new version was released on August 21, 2026.

The reason was not because Flutter was bad.

Flutter helped me build the previous version faster.

But for this application, I wanted more control over the Android experience, especially for:

  • Media playback
  • Performance
  • System integration
  • Long-term maintenance

Moving to native Android gives me a stronger foundation for future development.

Removing Features Was a Difficult Decision

The previous MTA ONE version had several features that were useful:

  • Qibla direction
  • Offline Quran
  • Prayer guidance
  • Daily prayers
  • Hijri calendar
  • Weather information

However, useful does not always mean it should stay inside the application.

Every feature has a cost.

A feature is not only about writing code once.

It requires maintenance afterward.

For example:

A weather feature requires weather data.

A Quran feature requires content management.

A calendar feature requires accuracy and updates.

When many features are combined into one application, the responsibility grows significantly.

I realized that if I wanted MTA ONE to continue improving, I needed to reduce the scope.

Returning to the Core of MTA ONE

MTA ONE is now focused on the features that are directly connected with MTA content.

MTA TV

The main video experience remains.

Users can watch MTA TV directly from the application with a simpler interface.

Online Radio

MTA ONE provides access to online radio channels from different regions:

  • Persada FM — Solo / Sragen
  • Suara Kesuma FM — Wonosobo
  • Persada FM Pacitan — Pacitan
  • Persada Bali FM — Bali
  • Skar FM — Madiun
  • Kharisma FM — Pontianak

The goal is simple:

Open the application, select a channel, and listen.

Weekly Brochure

Users can access the latest MTA weekly brochures.

Instead of keeping a large archive, MTA ONE focuses on providing the latest content that users frequently need.

Prayer Schedule

Prayer schedules are still available for cities and districts across Indonesia.

MTA Updates and Information

Users can also access:

  • Latest MTA news
  • MTA profile
  • Official study location information

A Smaller Application, A Better Direction

This rebuild taught me something:

More features do not always create a better application.

Sometimes, removing features allows the important parts to become better.

MTA ONE v4 is not a bigger application than before.

It is a more focused application.

With a smaller scope, I can spend more time improving:

  • Stability
  • Performance
  • User experience
  • Long-term maintenance

For a solo developer, focus is not just a preference.

It is a requirement.

MTA ONE v4 is the next step in that direction.

A simpler foundation for future improvements.

Try MTA ONE v4

MTA ONE v4 is now available.

You can download it from Google Play:

Download MTA ONE

Top comments (0)