dd3178c36e
* develop: (150 commits) Removes changelog file Fix PR comment Adds changelog file Refactors MessageBubbleView Updating changelog copy making use of the fake overrides for testing extracting the personalization complete emitting to a dedicated function making use of binding api instead of manual findviewbyid using consistent method naming for setting the capabilities override taking the personalization feature flag into account when calculating if personalization is supported - also removes a legacy loading workaround for the account creation step, we're navigating to a new screen AccountCreated so we have to stop the loading adding changelog entry using correct label for the avatar capability debug override forwarding to the profile picture flow when display name changing isn't supported but pictures are when personalising the profile formatting dynamically switching the onboarding flow based on the capabilities of the homeserver - when avatars can't be changed we complete the personlisation flow hiding the toolbar back button and handling system back as take the user home if the display name personalisation is not supported adding test around account creation via dummy dynamically changing the account created layout based on if the homeserver supports personalisation adding entry points for injecting and overriding the homeserver capabilities extracting method for the handling of the profile picture selection ... |
||
|---|---|---|
| .github | ||
| .idea | ||
| changelog.d | ||
| docs | ||
| fastlane | ||
| gradle/wrapper | ||
| library | ||
| matrix-sdk-android | ||
| matrix-sdk-android-flow | ||
| resources/img | ||
| tools | ||
| vector | ||
| vector-config | ||
| .editorconfig | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS.md | ||
| build.gradle | ||
| CHANGES.md | ||
| CONTRIBUTING.md | ||
| coverage.gradle | ||
| dependencies.gradle | ||
| dependencies_groups.gradle | ||
| Gemfile | ||
| Gemfile.lock | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| integration_tests_script.sh | ||
| integration_tests_script_github.sh | ||
| LICENSE | ||
| README.md | ||
| settings.gradle | ||
| towncrier.toml | ||
Element Android
Element Android is an Android Matrix Client provided by Element. The app can be run on every Android devices with Android OS Lollipop and more (API 21).
It is a total rewrite of Riot-Android with a new user experience.
Nightly build: Nighly test status: 
New Android SDK
Element is based on a new Android SDK fully written in Kotlin (like Element). In order to make the early development as fast as possible, Element and the new SDK currently share the same git repository.
At each Element release, the SDK module is copied to a dedicated repository: https://github.com/matrix-org/matrix-android-sdk2. That way, third party apps can add a regular gradle dependency to use it. So more details on how to do that here: https://github.com/matrix-org/matrix-android-sdk2.
Roadmap
The version 1.0.0 of Element still misses some features which was previously included in Riot-Android. The team will work to add them on a regular basis.
Releases to app stores
There is some delay between when a release is created and when it appears in the app stores (Google Play Store and F-Droid). Here are some of the reasons:
- Not all versioned releases that appear on GitHub are considered stable. Each release is first considered beta: this continues for at least two days. If the release is stable (no serious issues or crashes are reported), then it is released as a production release in Google Play Store, and a request is sent to F-Droid too.
- Each release on the Google Play Store undergoes review by Google before it comes out. This can take an unpredictable amount of time. In some cases it has taken several weeks.
- In order for F-Droid to guarantee that the app you receive exactly matches the public source code, they build releases themselves. When a release is considered stable, Element staff inform the F-Droid maintainers and it is added to the build queue. Depending on the load on F-Droid's infrastructure, it can take some time for releases to be built. This always takes at least 24 hours, and can take several days.
If you would like to receive releases more quickly (bearing in mind that they may not be stable) you have a number of options:
- Sign up to receive beta releases via the Google Play Store.
- Install a release APK directly - download the relevant .apk file and allow installing from untrusted sources in your device settings. Note: these releases are the Google Play version, which depend on some Google services. If you prefer to avoid that, try the latest dev builds, and choose the F-Droid version.
- If you're really brave, install the very latest dev build - click on Assemble (GPlay or FDroid) Debug version then on Artifacts.
Contributing
Please refer to CONTRIBUTING.md if you want to contribute on Matrix Android projects!
Come chat with the community in the dedicated Matrix room.
Triaging issues
Issues are triaged by community members and the Android App Team, following the triage process.
We use issue labels to sort all incoming issues.