Team effort, but thank you!! I've just taken the next month and a half off to work on things full time. I'm excited!

The next update won't be huge, (Google required us to make all screens 'edge to edge'[0], which took up most of my time last month). I'm hoping for some solid improvements now that's out the way, once the release pipeline has returned to normal.

Feel free to get in touch if you fancy contributing.

[0] https://developer.android.com/develop/ui/views/layout/edge-t...

▲

fhub 9 hours ago | parent [-]

If you can get your agent of choice to run up the app in an emulator and navigate the whole thing taking screenshots then tasks like edge-to-edge can be pretty hands off.

The way I did it was to firstly get accessibility identifiers on everything. Then have it record everything I do on an emulator to navigate the entire app. Then left it for a while to work out how to actually use the app via the emulator. Once you have this sort of baseline. A lot of changes are really quite pleasant. I often ask for an HTML gallery of screenshots covering a few device sizes as the step before I bother running it on a device myself.

▲

david_allison 9 hours ago | parent [-]

We use Roborazzi[0], which is an excellent screenshot library, but:

* We target minSdk 24

* We're still using XML views

* We target a large variety of form factors

* We have a lot of screens, and these have a lot of configuration options.

I really wish it was "point an agent at it, and walk away", but many screens ended up being hours of iteration with Fable driving my phone/an emulator to produce an acceptable outcome.

Given that my Pixel 9 Pro has system screens which are still broken under edge to edge, it's not an easy change, and takes up time which could have been going towards feature development.

[0] https://github.com/takahirom/roborazzi/

	▲	voakbasda 7 hours ago \| parent [-]
		Gotta love that Google enforces rules on developers that it won’t even enforce on itself. Such a great look.