pebble
  • Tutorials
  • Get the SDK
  • Guides
  • Documentation
  • PebbleOS
  • Mobile App
  • Examples
  • Index 01
  • Community
  • Blog
  • More
Privacy
Cookies
Publish

Mobile App

  • Overview
  • Contributing

Contributing to the Mobile App

The Pebble mobile app is developed at github.com/coredevices/mobileapp. The public repository is a copy of the internal one that Core Devices works in, synced by hand, so it can lag behind. Changes arrive as pull requests.

Sending a Change

  • Fork the repository and make the change on a branch.
  • Open a pull request against main. Say in the description what the change does and how you tested it.
  • If you used AI to write any of the code, say so in the description. The maintainers do not accept changes that the author has not read and understood.
  • Contributions to libpebble3 need the Contributor License Agreement. There is no sign-off requirement on commits.

Core Devices has a small mobile team, and reviewing a change can mean testing it with hardware and maintaining it afterwards, so a review can take some time. A pull request that adds a feature the team has not planned is more likely to wait than a fix.

Bugs in the app are reported from the app itself, under Settings, Get Help, New Bug Report, rather than as GitHub issues. The in-app report attaches the logs the team needs.

Forks

Maintaining a fork is fine. A fork may not use "Pebble" in its name except to refer to the watch, so "Awesome App for Pebble" is acceptable and "Pebble Awesome" is not. The repository README has the details.

License

The app is dual-licensed by Core Devices LLC. It can be used under the GNU GPLv3, or under a paid commercial license agreed with Core Devices. The GPL grant carries an additional permission to distribute builds through the Apple App Store.

Overview

  • Sending a Change
  • Forks
  • License