Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
135 lines (97 sloc) 7.29 KB

Android Floating Tutorial Activity

This README discusses the usage of the tutorial in Java rather than Kotlin. Kotlin usage is shown in the The Java and Kotlin sample apps are functionally equivalent.


You will need to create a new Activity that extends FloatingTutorialActivity and implements the FloatingTutorialActivity#getPages function:

public class ExampleActivity extends FloatingTutorialActivity {
    public List<TutorialPage> getPages() {
        return new ArrayList<TutorialPage>();

That function will return the list of pages that the user will see. The simplest implementation of providing a page would look like this:

public List<TutorialPage> getPages() {
    List<TutorialPage> pages = new ArrayList<>();

    pages.add(new TutorialPage(this) {
        public void initPage() {

    return pages;

A TutorialPage is similar to an Activity or Fragment. After you have used the setContentView function, you can manipulate those Views with the findViewById method. The tutorial pages do not enforce any UI standards for the content, so you can design these layouts to be whatever you want. Each page will automatically get the "Next" button and the progress indicators added, unless you specifically remove them.

To customize the look of the page, there are numerous options available:

new TutorialPage(context) {
    public void initPage() {
        // set the layout for the individual page

        // manipulate views however you want
        View view = findViewById(

        // Customize the look of the page
        hideNextButton();                          // useful if you want to handle going to the next page, within your layout, instead of with this button
        setNextButtonColor(Color.WHITE);           // you can also provide a color resource value with the setNextButtonColorResource function
        setNextButtonText("New Text");             // you can also provide a string resource value
        setProgressIndicatorColor(Color.WHITE);    // you can also provide a color resource value with the setProgressIndicatorColorResource function
        setBackgroundColor(Color.BLACK);           // the default background color is white. Changing it here will automatically adjust the progress indicator and next button colors, based on whether or not the background is light or dark.

Any other customization can come directly from your layout file. My examples show the primary color for the background of the top text. You could do that inside of your layout, if you like that look.

Animating the layouts

In my examples, as well as my own usage of this library, I like to provide subtle animations the first time that a user views a TutorialPage. If they were to go backwards in the tutorial, then return to a page for a second time, I do not show the animation again. If you would like to animate your pages in this way, you can override the TutorialPage#animateLayout function.

new TutorialPage(context) {

    public void animateLayout() {
        View view = findViewById(;

        // do some animation here. I have an example animation that you could use:
        AnimationHelper.quickViewReveal(view, 300);

If you would rather animate the View every time the page is shown, you could override the TutorialPage#onShown(firstTimeShown: Boolean) method, instead. If you override that, be sure to call the super class method.

Providing TutorialPage and Activity Results

Sometimes, you may need store and provide some kind of state within the tutorial. For example: if you are using the tutorial to log in a user, you will probably need the calling Activity to know if the login was successful or not.

Please see the SelectionDialogExample as an example of providing the calling Activity the result of your FloatingTutorialActivity.

Other times, you may need to know the result of the previous page, to display the UI for the next page. In the RateItExample, the first page asks the user to give a thumbs up or thumbs down.

  • If the user selects thumbs down, the second page will ask them if they want to provide feedback.
  • If the user selects thumbs up, the second page will ask them if they want to rate the app on the Play Store.

This is a good example of the need to communicate the previous page's result to the current page, and customizing the current page, based on that result.

Examples Explained

The sample app comes with a few different examples, highlighting different functionality:

  • SimpleDialogExample: a quick and nice looking replacement for an alert dialog, if you want it. This demonstrates a single page and some of the animation capabilites.
  • SelectionDialogExample: this demonstrates a selection process. It will provide the selection result as the Activity result.
  • FeatureWalkthroughExample: this is a simple feature tutorial that could be used anywhere in your apps. It also demonstrates changing the background color and providing multiple pages.
  • RateItExample: as discussed above, this example demonstrates passing data between the current and the previous page and manipulating the page, based on that data.
  • PulseSmsPurchaseExample: this demonstrates one way that I have used the floating-tutorial in Pulse SMS. It demonstrates more complex layouts and animations, as well as an Activity result.


Copyright 2017 Luke Klinker

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.