Fabulous FABs - sliding in and out in sync with the AppBarLayout

Juliane Lehmann / Fri, Jun 3, 2016

Edit: The code from this post became a library and got significant enhancements. It’s open source, so just look it up on github for the source code and instructions on using it as a gradle dependency.

Just want the goods without explanation? See this gist.

Picture a list view, with a Floating Action Button (FAB) sitting on it, like this:

The FAB needs to be able to move out of the way, so that all parts of all list items are actually reachable. Also, it is good form in this situation to have the app bar scroll out of the way, to maximise the viewport area dedicated to the list. There’s a well-known ready-made solution for this; it looks like this

and has two disadvantages:

Here’s how to get the FAB to move in sync with the app bar.

QuickFit 1.2 released

Juliane Lehmann / Thu, Jun 2, 2016

QuickFit now features a beautiful wide layout, for use on tablets in landscape mode. See:

A post or two on how to implement this fabulous FAB behavior is to follow.

This release also fixes a bug; scheduled activities do now really get cleared by clicking on the notification and will not reappear together with the next alert.

QuickFit is free on Google Play, or be a beta tester

Find the source (Apache License 2.0) on GitHub

I’d be happy about feedback on reddit, or raise an issue on GitHub.

Automating play store screenshots for fun and additional testing

Juliane Lehmann / Tue, Apr 12, 2016

Taking screenshots for the play store is boring as hell: several locales, three form factors, setting up content data for the screenshots, possibly varying by locale… For the last release of QuickFit, I decided to automate.

xkcd says it was worth it

xkcd says it was worth it (xkcd)

What you get in this post

And because UI tests are needed and a happy byproduct of the process, it comes with

I’ll walk you through my journey on automating the screenshots for the QuickFit app. It’s open source, [on github][github-quickfit] and on the [play store][playstore-quickfit]. [github-quickfit]: [playstore-quickfit]:

QuickFit 1.1 released

Juliane Lehmann / Mon, Apr 11, 2016

QuickFit now allow scheduling workouts on a weekly repeating basis!

This update is all about taking even more thought and effort out of tracking workouts with Google Fit: Set up once when you plan doing your workouts, and then get reminded via a notification to actually do it, and to enter your session into Google Fit. The focus is still on delivering minimal UI that allows the user to get all needed information as fast as possible.

New app: QuickFit

Juliane Lehmann / Wed, Feb 24, 2016

I’m learning Android development, and after hacking on Watchlater for a while, it was time for the first project completely of my own, that should also allow me to try my hand at some framework component that Watchlater simply had no use for. That project lies dormant on my HDD - while it taught me about the support library, material design and all about the service lifecycle, ultimately my goal of writing the IRC client I wanted was doomed from the start. The IRC protocol simply does not allow to identify users persistently, and so my goal of presenting query conversations on the same level as channels was unreachable. So QuickFit is the much better replacement project.

For me, using Google Fit is about logging my activity, looking at the calendar view and seeing a nice, high level and getting my daily pling. So walking and cycling gets tracked nicely automatically, but of course I want to enter my other workouts too. The Google Fit app can do this, but it is a bit of a long process: select the activity from the dropdown (easy, with the favorites), enter a time span, hit submit, get the “activity is in the future” message, go back, decide on some easy-to-enter start time that will work, hit submit again. That should be easier!

There was my perfect excuse for an app that allows me to:

Available for free on Google Play, or be a beta tester

Find the source (Apache License 2.0) on GitHub

I’d be happy about feedback by mail, or raise an issue on GitHub.

more posts ->