Why build my own Android automation app after more than 10 years of using other
For more than a decade, I've been a heavy user of Android automation apps. They have helped me automate repetitive tasks, customize device behavior, and make my phones work exactly the way I wanted.
Over the years, I tried many different solutions. Some were incredibly powerful, offering endless possibilities through complex workflows, scripting capabilities, and hundreds of triggers and actions. While these apps were impressive, I kept running into the same problem: they were often too complicated for simple automation.
What should have been a 10-second setup frequently turned into several minutes of navigating menus, understanding terminology, and configuring multiple options. The more features these apps added, the steeper the learning curve became.
At the same time, Android devices have evolved dramatically. While modern flagship phones have more than enough power to run large automation frameworks, many people still use older devices, secondary phones, tablets, or budget smartphones. These devices don't always benefit from apps that consume significant storage, memory, and background resources.
That realization planted a seed in my mind years ago. One day, I wanted to create an automation rule that was extremely simple. As I was setting it up, I found myself thinking: "Why does something this simple require so many steps?" That question eventually became the foundation of a new project.
## Building RuleRunner
I've always wanted to develop an Android app of my own. As a software enthusiast, creating something that people could actually use has been a long-term goal.
Recently, while working on a rules engine project, I realized I finally had the opportunity to build the automation app I had always envisioned. That's how RuleRunner was born.
RuleRunner is built around these core principles:
### 1. Privacy and Control First
Reason I wanted to build RuleRunner was to rethink the permissions model commonly used by automation apps.
Many automation tools request Accessibility Service permissions. While Accessibility Services are incredibly powerful and enable advanced automation, they also grant broad visibility and interaction capabilities across your device. In practice, this means the app can observe and interact with much of what happens on your phone.
For RuleRunner, I wanted a different approach. By default, RuleRunner does **not** require Accessibility Service permissions. Users can create and run automation rules without granting an app extensive control over their device. This keeps setup simple while reducing unnecessary permissions.
For users who want more advanced capabilities, RuleRunner can integrate with **Shizuku**, unlocking additional functionality through Android's system APIs without relying on Accessibility Services. The choice remains entirely with the user. My goal is simple: provide powerful automation while respecting user privacy, security, and control over their own devices. I believe automation should be accessible to everyone, not just power users willing to spend time learning complex systems or granting extensive device access.
### 2. Small and Lightweight
The goal is to keep the app lean and efficient.
I want RuleRunner to run smoothly not only on the latest Android devices but also on older phones that may have limited storage and memory. Automation shouldn't require a powerful device.
A lightweight app means:
* Faster installation
* Lower memory usage
* Less battery impact
* Better performance on older hardware
### 3. Simple Rules in Seconds
Most people don't need hundreds of settings to automate a simple task.
If your goal is something straightforward like:
* Turn on Wi-Fi when arriving home
* Launch an app when headphones connect
* Enable silent mode during work hours
* Perform an action when battery reaches a certain level
You shouldn't need to study a manual first. My vision for RuleRunner is that simple automations can be created in around 10 seconds. Select a trigger, choose an action, save the rule, and you're done. No complicated setup screens. No overwhelming configuration options. Just automation that works.
## Focusing on the Rules Engine
One of the most exciting parts of developing RuleRunner has been working on the rules engine itself. A good automation platform is only as strong as its underlying engine. By focusing on flexibility at the engine level, RuleRunner can remain simple on the surface while still growing in capability over time. The challenge is finding the right balance between power and simplicity. Users should be able to create advanced automations when needed, but simple tasks should remain simple. That's the philosophy guiding the development of RuleRunner.
## Looking Ahead
RuleRunner is more than just another Android automation app. It's my attempt to build the automation tool I always wished existed after spending more than ten years using others.
An app that is lightweight.
An app that respects older devices.
An app that doesn't overwhelm users with complexity.
And most importantly, an app that allows simple automation rules to be created in seconds.
RuleRunner is my attempt to create the automation app I've wanted to use for years: fast, lightweight, easy to understand, and respectful of the user's control over their own device. The journey is still ongoing, and there is plenty more to build.
Over the years, I tried many different solutions. Some were incredibly powerful, offering endless possibilities through complex workflows, scripting capabilities, and hundreds of triggers and actions. While these apps were impressive, I kept running into the same problem: they were often too complicated for simple automation.
What should have been a 10-second setup frequently turned into several minutes of navigating menus, understanding terminology, and configuring multiple options. The more features these apps added, the steeper the learning curve became.
At the same time, Android devices have evolved dramatically. While modern flagship phones have more than enough power to run large automation frameworks, many people still use older devices, secondary phones, tablets, or budget smartphones. These devices don't always benefit from apps that consume significant storage, memory, and background resources.
That realization planted a seed in my mind years ago. One day, I wanted to create an automation rule that was extremely simple. As I was setting it up, I found myself thinking: "Why does something this simple require so many steps?" That question eventually became the foundation of a new project.
## Building RuleRunner
I've always wanted to develop an Android app of my own. As a software enthusiast, creating something that people could actually use has been a long-term goal.
Recently, while working on a rules engine project, I realized I finally had the opportunity to build the automation app I had always envisioned. That's how RuleRunner was born.
RuleRunner is built around these core principles:
### 1. Privacy and Control First
Reason I wanted to build RuleRunner was to rethink the permissions model commonly used by automation apps.
Many automation tools request Accessibility Service permissions. While Accessibility Services are incredibly powerful and enable advanced automation, they also grant broad visibility and interaction capabilities across your device. In practice, this means the app can observe and interact with much of what happens on your phone.
For RuleRunner, I wanted a different approach. By default, RuleRunner does **not** require Accessibility Service permissions. Users can create and run automation rules without granting an app extensive control over their device. This keeps setup simple while reducing unnecessary permissions.
For users who want more advanced capabilities, RuleRunner can integrate with **Shizuku**, unlocking additional functionality through Android's system APIs without relying on Accessibility Services. The choice remains entirely with the user. My goal is simple: provide powerful automation while respecting user privacy, security, and control over their own devices. I believe automation should be accessible to everyone, not just power users willing to spend time learning complex systems or granting extensive device access.
### 2. Small and Lightweight
The goal is to keep the app lean and efficient.
I want RuleRunner to run smoothly not only on the latest Android devices but also on older phones that may have limited storage and memory. Automation shouldn't require a powerful device.
A lightweight app means:
* Faster installation
* Lower memory usage
* Less battery impact
* Better performance on older hardware
### 3. Simple Rules in Seconds
Most people don't need hundreds of settings to automate a simple task.
If your goal is something straightforward like:
* Turn on Wi-Fi when arriving home
* Launch an app when headphones connect
* Enable silent mode during work hours
* Perform an action when battery reaches a certain level
You shouldn't need to study a manual first. My vision for RuleRunner is that simple automations can be created in around 10 seconds. Select a trigger, choose an action, save the rule, and you're done. No complicated setup screens. No overwhelming configuration options. Just automation that works.
## Focusing on the Rules Engine
One of the most exciting parts of developing RuleRunner has been working on the rules engine itself. A good automation platform is only as strong as its underlying engine. By focusing on flexibility at the engine level, RuleRunner can remain simple on the surface while still growing in capability over time. The challenge is finding the right balance between power and simplicity. Users should be able to create advanced automations when needed, but simple tasks should remain simple. That's the philosophy guiding the development of RuleRunner.
## Looking Ahead
RuleRunner is more than just another Android automation app. It's my attempt to build the automation tool I always wished existed after spending more than ten years using others.
An app that is lightweight.
An app that respects older devices.
An app that doesn't overwhelm users with complexity.
And most importantly, an app that allows simple automation rules to be created in seconds.
RuleRunner is my attempt to create the automation app I've wanted to use for years: fast, lightweight, easy to understand, and respectful of the user's control over their own device. The journey is still ongoing, and there is plenty more to build.
Rule examples
- Detect when Bluetooth is enabled or connected, then launch a music app and adjust volume automatically.
- Automatically set the device to silent mode when enter a place of worship.
- Schedule automatic mute and unmute at specific times.
- Enable auto-rotate for selected games or video apps.
- Trigger an alert sound when the battery is fully charged.
- Open specific apps directly when receiving notifications from selected apps.
- Manage moving or deleting of files.
- Switch keyboard language automatically for apps that require a different input language.
- Automatically dismiss notifications from selected apps.
- Launch GPay automatically when NFC is enabled.