In the coming week, I will finally focus on more options to login.

Last week I cleaned up UI code and added the retry button to the Error screen, as I said.

Check homeserver capabilities

When clicking the "Check" button the Client should figure out what login methods are actually supported. This is especially mandatory for OAuth login.

The function to do so is already present, I just never actually hooked it up to the button.

Login with Username and Password

Logging in via homeserver is already implemented, the two missing methods are OAuth and Username + Password.

If you are interested in meteorite, contributions are always (very) welcome!

That's all for this week. See you next week!

This week, I will focus on cleaning up meteorite's UI code.

Last week I added everything I talked about and a few more things, which I mostly found out about via the new CI Checks.

For example I removed a crate used to previously display errors before the UI started. I isolated the errors that could happen and just passed them into the UI.

UI cleanup

The UI currently determines what to display via different states which are manually set.

Instead I would like each different screen (e.g. Login) to be a callable function. This would greatly simplify redirections from the main screen to the login screen and back.

The other thing I would like to do is adding a retry button to the error screen. Most errors are recoverable if re-attempted.

If you are interested in meteorite, contributions are always (very) welcome!

That's all for this week. See you next week!

This week, I’m planning to focus on improving meteorite's mobile support and cleaning up some of the login code.

Mobile checks

First, I want to add my Rust checks to both Android and iOS. The goal is to make sure meteorite continues to compile on mobile as development continues, before I start adding more mobile-specific functionality.

There were already a few changes needed to make this possible. For example, I switched to a different crate for resolving the save path, since the one I was using previously doesn't support Android.

Android keyring

The mobile checks also depend on a missing piece of meteorite's Android support: there currently isn't an Android keyring implementation.

So, I’m planning to work on adding native Android keyring support this week as well.

Login cleanup

While working on the keyring, I also want to clean up the login code.

At the moment, some of the login functionality is more intertwined than I’d like, so I’m going to split it into smaller helper functions. This will include things like loading the currently saved account data and saving new account data.

So, the plan for this week is to get the mobile checks in place, add the Android keyring, and make the login code a little easier to work with.

If you are interested in meteorite, contributions are always (very) welcome!

That's all for this week. See you next week!