New app: MoodyRoutine

Abstract

Please introduce the functions and usage of your app in summary, and also attach some screenshots.

MoodyRoutine brings Samsung One UI-style contextual automation and situational profiles to any Android device running Android 8.0+ without requiring root or manufacturer-locked frameworks:

• Modes (Situational Profiles): Bundles device settings into persistent profiles (Sleep, Work, Driving, Exercise, Relax, Custom) with ongoing notification shade controls, state reversion, and an app blocker ("Stay Focused").
• Routines (IF -> THEN): Event-driven automation based on Schedule, Battery, Wi-Fi SSID, Bluetooth devices, App open/close, Headphones, and OpenStreetMap geofences, with automatic state restoration.
• Privacy & FOSS: 100% libre, zero ads, zero trackers, licensed under GPL-3.0. Features a dedicated foss product flavor using native AOSP LocationManager instead of Google Play Services.

Screenshots and full metadata are available in the upstream repository under fastlane/metadata/: https://github.com/naman-chopra/moody-routine#screenshots

Please elaborate why you wrote this app. Please highlight the unique functions it provides over other similar apps in F-Droid.

Most existing automation apps on Android either:

1. Have very steep learning curves with complex syntax (e.g. Tasker, Automate).
2. Push subscriptions, mandatory user accounts, or proprietary analytics.
3. Lack clean, ergonomic situational profiles like Samsung One UI's native Modes & Routines.

MoodyRoutine fills this gap on F-Droid by delivering an intuitive, thumb-friendly One UI design focused on daily ergonomics, clean profile switching, and simple IF/THEN automation that requires no programming knowledge.

Checklist

Policy

• The app complies with the inclusion criteria.
• The original app author has been notified (and does not oppose the inclusion). (I am the author).
• The upstream app source code repo contains the app metadata in a Fastlane or Triple-T folder structure. The summary and description must be included and images, icon, and changelog should also be provided for better user experience. The en-US locale must be included.

Docs

• Please read the guide first if this is your first contribution.
• Please make sure your metadata follows the best practice in our templates.
• Please read the Build Metadata Reference and make sure your metadata is valid.
• Please read the Quick Start Guide.

Merge Request Setup

• The title of this merge request should follow "New app: app name" format.
• Please make sure your fdroiddata fork is public and your branch is not protected. See https://docs.gitlab.com/user/project/repository/branches/protected/.
• Please read our Git guide if you don't know how to rebase your branch. Don't rebase your branch if there is no conflict.
• All related fdroiddata and RFP issues have been referenced in this merge request
• Please only submit one app in one MR.

Metadata

• Metadata must be put in metadata/<applicationId>.yml.
• Metadata must be a valid YAML file.
• Metadata must use LF as line ending.
• Don't add summary/description/changelog/images or anything that should be provided in upstream repo. Please check the Changes tab to make sure there is no other unrelated files added in the MR.
• Releases are tagged and auto update is enabled unless there is a special reason.
• There is an issue tracker and contact info of the author so that we can report bugs and contact the author.
• An AuthorName must be added. It doesn't need to be the real name.
• External repos are added as git submodules instead of srclibs.
• Enable Reproducible Builds. (The initial v1.0.0 GitHub release asset was built before separating the foss and gms flavors, so it contains Play Services. Standard F-Droid signing is used for v1.0.0; reproducible builds will be enabled from v1.0.1 onwards).
• Setup abi split if the APK is large and the splitted ones can be much smaller.
• Only the latest versions should be kept in the metadata before it's merged.
• Don't add any disabled versions in the metadata.
• The commit field should be the full hash. Please don't use tag or branch in commit.

Pipeline

• All pipelines should pass.
• All warnings and errors in the Reports tab should be fixed or explained.
• F-Droid CI runners are under GitLab's FOSS program, so there's no need for you to pay for any CI time. If Gitlab starts asking for phone numbers or credit cards don't submit anything, just leave a note in the MR so we know we need to trigger the CI.