Need help with AppIntro?
Click the โ€œchatโ€ button below for chat support from the developer who created it, or find similar developers for support.

About the developer

9.6K Stars 1.7K Forks Apache License 2.0 839 Commits 28 Opened issues


Make a cool intro for your Android app.

Services available


Need anything else?

Contributors list


Join the chat at Pre Merge Checks Android Arsenal Awesome Kotlin Badge

AppIntro is an Android Library that helps you build a cool carousel intro for your App. AppIntro has support for requesting permissions and helps you create a great onboarding experience in just a couple of minutes.

appintro icon appintro sample

Getting Started ๐Ÿ‘ฃ

AppIntro is distributed through JitPack.

Adding a dependency

To use it you need to add the following gradle dependency to your

file of the module where you want to use AppIntro (NOT the root file).
repositories {
    maven { url "" }
dependencies {
    // AndroidX Capable version
    implementation 'com.github.AppIntro:AppIntro:6.0.0'

// *** OR ***

// Latest version compatible with the old Support Library
implementation 'com.github.AppIntro:AppIntro:4.2.3'


Please note that since AppIntro 5.x, the library supports Android X. If you haven't migrated yet, you probably want to use a previous version of the library that uses the old Support Library packages (or try Jetifier Reverse mode).

Basic usage

To use AppIntro, you simply have to create a new Activity that extends AppIntro like the following:

class MyCustomAppIntro : AppIntro() {
    override fun onCreate(savedInstanceState: Bundle?) {
        // Make sure you don't call setContentView!

    // Call addSlide passing your Fragments.
    // You can use AppIntroFragment to use a pre-built fragment
            title = "Welcome...",
            description = "This is the first slide of the example"
            title = "...Let's get started!",
            description = "This is the last slide, I won't annoy you more :)"

override fun onSkipPressed(currentFragment: Fragment?) {
    // Decide what to do when the user clicks on "Skip"

override fun onDonePressed(currentFragment: Fragment?) {
    // Decide what to do when the user clicks on "Done"


Please note that you must NOT call setContentView. The

superclass is taking care of it for you.

Finally, declare the activity in your Manifest like so:

We suggest to don't declare

as your first Activity unless you want the intro to launch every time your app starts. Ideally you should show the AppIntro activity only once to the user, and you should hide it once completed (you can use a flag in the

Migrating ๐Ÿš—

If you're migrating from AppIntro v5.x to v6.x, please expect multiple breaking changes. You can find documentation on how to update your code on this other migration guide.

Features ๐Ÿงฐ

Don't forget to check the changelog to have a look at all the changes in the latest version of AppIntro.

  • API >= 14 compatible.
  • 100% Kotlin Library.
  • AndroidX Compatible.
  • Support for runtime permissions.
  • Dependent only on AndroidX AppCompat/Annotations, ConstraintLayout and Kotlin JDK.
  • Full RTL support.

Creating Slides ๐Ÿ‘ฉโ€๐ŸŽจ

The entry point to add a new slide is the

addSlide(fragment: Fragment)
function on the
class. You can easily use it to add a new
to the carousel.

The library comes with several util classes to help you create your Slide with just a couple lines:


You can use the

if you just want to customize title, description, image and colors. That's the suggested approach if you want to create a quick intro:
    title = "The title of your slide",
    description = "A description that will be shown on the bottom",
    imageDrawable = R.drawable.the_central_icon,
    backgroundDrawable = R.drawable.the_background_image,
    titleColor = Color.YELLOW,
    descriptionColor = Color.RED,
    backgroundColor = Color.BLUE,
    titleTypefaceFontRes = R.font.opensans_regular,
    descriptionTypefaceFontRes = R.font.opensans_regular,

All the parameters are optional, so you're free to customize your slide as you wish.

If you need to programmatically create several slides you can also use the

class. This class can be passed to
AppIntroFragment.newInstance(sliderPage: SliderPage)
that will create a new slide starting from that instance.


If you need further control on the customization of your slide, you can use the

. This will allow you pass your custom Layout Resource file:

This allows you to achieve complex layout and include your custom logic in the Intro (see also Slide Policy):

appintro custom-layout

Configure ๐ŸŽจ

AppIntro offers several configuration option to help you customize your onboarding experience.

Slide Transformer

AppIntro comes with a set of Slide Transformer that you can use out of the box to animate your Slide transition.

| Slide Transformers | Slide Transformers | | :---: | :---: | | Fade
fade | Zoom
zoom | | Flow
flow | Slide Over
slideover | | Depth
depth | Parallax
parallax |

You can simply call

and pass one of the subclass of the sealed class

// You can customize your parallax parameters in the constructors. setTransformer(AppIntroPageTransformerType.Parallax( titleParallaxFactor = 1.0, imageParallaxFactor = -1.0, descriptionParallaxFactor = 2.0 ))

Custom Slide Transformer

You can also provide your custom Slide Transformer (implementing the

interface) with:

Color Transition

appintro sample

AppIntro offers the possibility to animate the color transition between two slides background. This feature is disabled by default, and you need to enable it on your AppIntro with:

isColorTransitionsEnabled = true

Once you enable it, the color will be animated between slides with a gradient. Make sure you provide a

parameter in your slides.

If you're providing custom Fragments, you can let them support the color transition by implementing the


Multiple Windows Layout

AppIntro is shipped with two top-level layouts that you can use. The default layout (

) has textual buttons, while the alternative layout has buttons with icons.

To change the Window layout, you can simply change your superclass to

. The methods to add and customize the AppIntro are unchanged.
class MyCustomAppIntro : AppIntro2() {
    // Same code as displayed in the `Basic Usage` section of this README

| Page |

| | ---: | :--------: | :---------: | | standard page | layout1-start | layout2-start | | last page | layout1-end | layout2-end |


AppIntro supports two indicators out of the box to show the progress of the Intro experience to the user:

  • DotIndicatorController
    represented with a list of Dot (the default)
  • ProgressIndicatorController
    represented with a progress bar.


| | ---------- | ----------- | | dotted indicator | progress indicator |

Moreover, you can supply your own indicator by providing an implementation of the


You can customize the indicator with the following API on the

// Toggle Indicator Visibility                
isIndicatorEnabled = true

// Change Indicator Color setIndicatorColor( selectedIndicatorColor = getColor(, unselectedIndicatorColor = getColor( )

// Switch from Dotted Indicator to Progress Indicator setProgressIndicator()

// Supply your custom IndicatorController implementation indicatorController = MyCustomIndicator(/* initialize me */)

If you don't specify any customization, a

will be shown.


AppIntro supports providing haptic vibration feedback on button clicks. Please note that you need to specify the Vibration permission in your app Manifest (the library is not doing it). If you forget to specify the permission, the app will experience a crash.

You can enable and customize the vibration with:

// Enable vibration and set duration in ms
isVibrate = true
vibrateDuration = 50L

Wizard Mode

appintro wizard1 appintro wizard2

AppIntro supports a wizards mode where the Skip button will be replaced with the back arrow. This comes handy if you're presenting a Wizard to your user with a set of skip they need to do, and they might frequently go back and forth.

You can enable it with:

isWizardMode = true

Immersive Mode

appintro immersive1 appintro immersive2

If you want to display your Intro with a fullscreen experience, you can enable the Immersive mode. This will hide both the Status Bar and the Navigation bar and the user will have to scroll from the top of the screen to show them again.

This allows you to have more space for your Intro content and graphics.

You can enable it with:


System Back button

You can lock the System Back button if you don't want your user to go back from intro. This could be useful if you need to request permission and the Intro experience is not optional.

If this is the case, please set to true the following flag:

isSystemBackButtonLocked = true

System UI (Status Bar and Navigation Bar)

appintro system-ui

You can customize the Status Bar, and the Navigation Bar visibility & color with the following methods:

// Hide/Show the status Bar
// Control the status bar color

// Control the navigation bar color setNavBarColor(Color.RED) setNavBarColorRes(

Permission ๐Ÿ”’

appintro permissions

AppIntro simplifies the process of requesting runtime permissions to your user. You can integrate one or more permission request inside a slide with the

method inside your activity.

Please note that: *

is in a One-based numbering (it starts from 1) * You can specify more than one permission if needed * You can specify if the permission is required. If so, users can't proceed if he denies the permission.
// Ask for required CAMERA permission on the second slide. 
    permissions = arrayOf(Manifest.permission.CAMERA),
    slideNumber = 2, 
    required = true)

// Ask for both optional ACCESS_FINE_LOCATION and WRITE_EXTERNAL_STORAGE // permission on the third slide. askForPermissions( permissions = arrayOf( Manifest.permission.ACCESS_FINE_LOCATION, Manifest.permission.WRITE_EXTERNAL_STORAGE ), slideNumber = 3, required = false)

Should you need further control on the permission request, you can override those two methods on the

override fun onUserDeniedPermission(permissionName: String) {
    // User pressed "Deny" on the permission dialog
override fun onUserDisabledPermission(permissionName: String) {
    // User pressed "Deny" + "Don't ask again" on the permission dialog

Slide Policy

If you want to restrict navigation between your slides (i.e. the user has to toggle a checkbox in order to continue), the

feature might help you.

All you have to do is implement

in your slides.

This interface contains the

property and the
method that you must implement with your custom logic
class MyFragment : Fragment(), SlidePolicy {

// If user should be allowed to leave this slide
override val isPolicyRespected: Boolean
    get() = false // Your custom logic here.

override fun onUserIllegallyRequestedNextPage() {
    // User illegally requested next slide.
    // Show a toast or an informative message to the user.


You can find a full working example of

in the example app - CustomSlidePolicyFragment.kt

Example App ๐Ÿ’ก

AppIntro comes with a sample app full of examples and use case that you can use as inspiration for your project. You can find it inside the /example folder.

You can get a debug APK of the sample app from the Pre Merge Github Actions job as an output artifact here.

appintro sample app

Translating ๐ŸŒ

Do you want to help AppIntro becoming international ๐ŸŒ? We are more than happy! AppIntro currently supports the following languages.

To add a new translation just add a pull request with a new

file inside a
folder (where
is a two-letter ISO 639-1 language code).

In order to provide the translation, your file needs to contain the following strings:

    [Translation for SKIP]
    [Translation for NEXT]
    [Translation for BACK]
    [Translation for DONE]
    [Translation for "graphics"]

An updated version of the English version translation is available here.

If a translation in your language is already available, please check it and eventually fix it (all the strings should be listed, not just a subset).

Snapshots ๐Ÿ“ฆ

Development of AppIntro happens on the master branch. You can get

versions directly from JitPack if needed.
repositories {
    maven { url "" }
dependencies {
  implementation "com.github.AppIntro:AppIntro:master-SNAPSHOT"

โš ๏ธ Please note that the latest snapshot might be unstable. Use it at your own risk โš ๏ธ

Contributing ๐Ÿค

We're offering support for AppIntro on the #appintro channel on KotlinLang Slack. Come and join the conversation over there. If you don't have access to KotlinLang Slack, you can request access here.

We're looking for contributors! Don't be shy. ๐Ÿ‘ Feel free to open issues/pull requests to help me improve this project.

  • When reporting a new Issue, make sure to attach Screenshots, Videos or GIFs of the problem you are reporting.
  • When submitting a new PR, make sure tests are all green. Write new tests if necessary.

Acknowledgments ๐ŸŒธ


AppIntro is currently developed and maintained by the AppIntro Github Org. When submitting a new PR, please ping one of:


AppIntro is not relying on any third party library other than those from AndroidX:

  • androidx.appcompat:appcompat
  • androidx.annotation:annotation
  • androidx.constraintlayout:constraintlayout

License ๐Ÿ“„

    Copyright (C) 2015-2020 AppIntro Developers

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.

Apps using AppIntro ๐Ÿ“ฑ

If you are using AppIntro in your app and would like to be listed here, please open a pull request and we will be more than happy to include you:

List of Apps using AppIntro

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.