IssueTracker

Let's break down the automation features offered by Google Pixel (Rules), Samsung (Modes and Routines, formerly Bixby Routines), and Apple (Shortcuts), comparing their strengths and weaknesses, and then propose feature requests for Pixel's Rules.

Comparison of Pixel Rules, Samsung Routines, and Apple Shortcuts

Based on the comparison, Pixel's Rules feature is significantly lagging behind. Here are feature requests to improve it, following the requested format:

1. Expanded Triggers

• More information about the feature: Currently, Rules only supports Wi-Fi connection and location arrival as triggers. This is extremely limiting. We need a much broader range of triggers.
• What is the desired behavior of the feature?
  • Time-based triggers: Trigger Rules at specific times of day, days of the week, or on a recurring schedule (e.g., every Monday at 8 AM).
  • Device state triggers: Trigger Rules based on battery level (e.g., turn on battery saver when below 20%), charging status, Bluetooth connection (e.g., turn off Wi-Fi when connected to car Bluetooth), headphone connection, app usage (e.g., open a specific app when another app is launched), and notification content.
  • Sensor-based triggers: Trigger on device orientation, light levels, or other sensor data.
• If relevant, why are current approaches or workarounds insufficient? The current triggers are far too limited for any meaningful automation. Users are forced to use third-party apps like Tasker (which requires granting extensive permissions) or simply go without automation.
• If relevant, what new use cases will this feature enable?
  • Automatically turn on Do Not Disturb during scheduled meetings.
  • Turn on battery saver when the battery is low.
  • Mute the phone when connected to work Wi-Fi and unmute when leaving.
  • Start a music app when headphones are connected.
  • Launch a note-taking app when a specific app (e.g., a drawing app) is opened.

2. Expanded Actions

• More information about the feature: Rules currently only allows changing a few basic phone settings. We need more actions to control apps and device functionality.
• What is the desired behavior of the feature?
  • App control: Launch apps, send messages (SMS or through other messaging apps), control media playback (play, pause, skip), and interact with specific app features (if the app provides an API for this).
  • Device settings: Control a wider range of settings, including display brightness, Wi-Fi hotspot, Bluetooth, mobile data, volume for different audio streams, and more granular Do Not Disturb options.
  • Notification actions: Post custom notifications, dismiss notifications from specific apps, or modify notification settings.
  • System actions: Toggle airplane mode, set alarms.
• If relevant, why are current approaches or workarounds insufficient? The current actions are too basic to be truly useful. Users can't even perform simple tasks like starting a specific playlist when connecting to their car's Bluetooth.
• If relevant, what new use cases will this feature enable?
  • Automatically start a specific playlist when connecting to car Bluetooth.
  • Send a text message to a specific contact when arriving at a location.
  • Turn on the Wi-Fi hotspot when launching a specific app.
  • Set detailed do not disturb parameters.

3. Conditional Logic (If/Then/Else)

• More information about the feature: Rules currently operates on a simple "If trigger, then action" basis. There's no way to add conditions or create more complex logic.
• What is the desired behavior of the feature? Allow users to add "if" conditions to Rules. For example: "If I connect to my home Wi-Fi and the time is after 6 PM, then set the phone to silent." This would involve adding an interface to build these conditions using logical operators (AND, OR, NOT). Consider supporting "Else" statements for more complex branching logic.
• If relevant, why are current approaches or workarounds insufficient? Without conditional logic, Rules can't handle even slightly complex scenarios. Users are forced to create multiple Rules with overlapping triggers, which can lead to unexpected behavior.
• If relevant, what new use cases will this feature enable?
  • Only turn on Do Not Disturb at night if connected to home Wi-Fi (to avoid silencing the phone when away from home).
  • Only turn on battery saver if the battery is low and not charging.
  • Run a specific Rule only on weekdays.

4. Variables and Data Passing

• More information about the feature: There's currently no way to store or manipulate data within Rules.
• What is the desired behavior of the feature? Introduce the concept of variables that can store information (e.g., the current time, the name of the connected Wi-Fi network, the current location). Allow Rules to use these variables in actions. For example, a Rule could store the current volume level, mute the phone, and then restore the original volume level later.
• If relevant, why are current approaches or workarounds insufficient? The lack of variables prevents many useful automation scenarios.
• If relevant, what new use cases will this feature enable?
  • Store and restore the previous volume level.
  • Create a counter to track how many times a Rule has been triggered.
  • Use the current date/time in a notification message.

5. Third-Party App Integration

• More information about the feature: Rules currently focuses almost entirely on system settings.
• What is the desired behavior of the feature? Provide a way for third-party apps to expose actions that can be used in Rules. This would likely involve creating an API that app developers could use to integrate with Rules. This would be similar to how Shortcuts integrates with many iOS apps.
• If relevant, why are current approaches or workarounds insufficient? Without third-party app integration, Rules remains isolated from the broader app ecosystem.
• If relevant, what new use cases will this feature enable?
  • Start a specific workout in a fitness app when arriving at the gym.
  • Add a task to a to-do list app when connecting to work Wi-Fi.
  • Control smart home devices through their respective apps.

6. User Interface Improvements

• More information about the feature: The current Rules interface is very basic.
• What is the desired behavior of the feature?:
  • Provide a more visual and intuitive interface for creating and managing Rules.
  • Allow users to easily duplicate and edit existing Rules.
  • Include a way to test Rules without having to manually trigger them.
  • Offer a library of pre-built Rules for common tasks, similar to Shortcuts' gallery.
  • Enable/Disable specific rules [27]
• If relevant, why are current approaches or workarounds insufficient? The current interface makes it difficult to manage more than a few simple Rules.
• If relevant, what new use cases will this feature enable? This would improve the overall user experience and make Rules more accessible to a wider range of users.

By implementing these feature requests, Google could transform Rules from a barely-functional feature into a powerful automation tool that rivals Samsung's Routines and even approaches the capabilities of Apple's Shortcuts. This would significantly enhance the Pixel user experience and make the platform more competitive.