Newapp: lwidget

Abstract for new app inclusion

Summary & Functions

Lwidget is an ultra-lightweight, battery-efficient, privacy-first home screen widget designed around Android's Material You dynamic theming.

Key functions:

  • Time & Date Display: Supports custom font styles, custom formats, and native 12-hour/24-hour presentation.
  • Calendar Events: Seamless integration with device calendars (both synchronized and local calendars) displaying upcoming events.
  • Tasks Integration: Displays active and overdue task items via Tasks.org.
  • Local Weather: Displays current condition and temperature via Breezy Weather integration.
  • Hardware Pedometer: Live step counting using device hardware sensors without background wake locks.
  • Battery & Device Stats: Live battery level, temperature, charging status, device storage, and RAM monitors.
  • Alarms & World Clock: Displays next active alarm and secondary timezone clock.

Why this app was written & Unique features over existing widgets

Many home screen widgets on Android suffer from heavy battery drain due to constant background polling services, bloated dependencies, or lack of privacy. Lwidget was built with three fundamental design principles:

  1. Zero background wake locks & battery friendly: Leverages Android system broadcasts, hardware step sensors, and native RemoteViews/TextClock components. No perpetual background daemon or excessive battery drain.
  2. Completely private & offline-first: Requires zero network permissions. No analytics, tracking, or external cloud calls. Weather and tasks are read through local Android ContentProviders from trusted open-source apps (Breezy Weather and Tasks.org).
  3. Deep Material You dynamic theming: Adapts color palettes directly from the user's Android wallpaper across 10 custom typography styles.

Screenshots

Home Screen Widget Config & Font Styles
Widget Home Styles & Fonts
Events & Weather Stats & Battery

Checklist

Policy

  • The app complies with the inclusion policy. Pay special attention to Quality point 6.
  • The original app author has been notified (and does not oppose the inclusion). I am the original 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

Merge Request Setup

Metadata

  • Metadata must be put in metadata/.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. You can update git submodules without opening an MR in this repo and the submodule is covered by our scanner.
  • Enable Reproducible Builds. We'll use your signature for improved security/reliability, also allowing users to switch between different channels. Do note that if you don't enable reproducible build then the apk will be signed with our key so you can't enable it later. If you can't enable this, please add the reasons here.
  • Setup abi split if the APK is large and the splitted ones can be much smaller. (Lightweight single universal APK, ~2.1MB).
  • Only the latest versions should be kept in the metadata before it's merged. If you update the metadata, please replace the old versions with the new ones.
  • 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.

Merge request reports

Loading
Loading