Skip to content

jfilter/react-native-onboarding-swiper

Repository files navigation

<Onboarding /> npm npm

There are many ways to onboard people to your mobile app. But for React-Native, there is solely one component that is a) easy to setup and b) highly customizable: react-native-onboarding-swiper.

Your new users shouldn't jump in at the deep end. First give them a pleasurable, delightful introduction and only then let them explore your awesome app.

Getting everything running merely takes a minute. Try out the example running in your browser. Or check out this tutorial on YouTube.

Install

npm i react-native-onboarding-swiper
yarn add react-native-onboarding-swiper

Usage

import Onboarding from 'react-native-onboarding-swiper';

<Onboarding
  pages={[
    {
      backgroundColor: '#fff',
      image: <Image source={require('./images/circle.png')} />,
      title: 'Onboarding',
      subtitle: 'Done with React Native Onboarding Swiper',
    },
    ...
  ]}
/>

Examples

Check out the three examples files: the simple example, the example with a Call-to-Action button or the example with custom button components.

Required Properties

  • pages (required): an array of pages in the following shape:
    • backgroundColor (optional): a background color. The color of the font and dots adapts to the background color. Either backgroundColor or background should be provided.
    • background (optional): a React element rendered behind the page content (e.g. a <LinearGradient />). Use this for gradient or custom backgrounds without the library depending on any specific package. Can be combined with backgroundColor β€” the solid color provides smooth animated transitions between pages while the background element handles visuals.
    • isLight (optional): a bool to override automatic theme detection. When true, text and dots use dark colors; when false, they use light colors. Useful when using background since the library can't automatically detect brightness from a gradient. Defaults to false when neither backgroundColor nor isLight is provided.
    • image (required): a component (e.g. <Image />) to display at the top of the page.
    • title (required): a string OR a React-Native component.
    • subtitle (required): a string OR a React-Native component.

Optional Properties

Buttons

  • nextLabel (optional): a string OR a React-Native component for the Next label. Defaults to Next.
  • showNext (optional): a bool flag indicating whether the Next button is visible. Defaults to true.
  • skipLabel (optional): a string OR a React-Native component for the Skip label. Defaults to Skip.
  • showSkip (optional): a bool flag indicating whether the Skip button is visible. Defaults to true.
  • onSkip (optional): a callback that is fired if the Onboarding is skipped.
  • skipToPage (optional): when pressing skip, go to that page (e.g. skipToPage={2}). If this prop is provided, ignores onSkip.
  • onNext (optional): a callback that is fired when the Next button is pressed.
  • onDone (optional): a callback that is fired after the Onboarding is completed.
  • showDone (optional): a bool flag indicating whether the Done checkmark button is visible. Defaults to true.

General

  • bottomBarHeight (optional): a number for the height of the bottom bar. Defaults to 60.
  • bottomBarColor (optional): backgroundColor of the bottom bar. Defaults to transparent.
  • bottomBarHighlight (optional): a bool flag indicating whether the bottom bar should be highlighted. Defaults to true.
  • controlStatusBar (optional): a bool flag indicating whether the status bar should change with the background color. Defaults to true.
  • showPagination (optional): whether to show the bottom pagination bar. Defaults to true.
  • flatlistProps (optional): additional props for the FlatList which holds all the pages.
  • transitionAnimationDuration (optional): The duration in milliseconds for the animation of the background color for the page transition. Defaults to 500.
  • allowFontScalingText (optional): Font scaling can cause troubles with high-resolution screens. You may want to disable it. Defaults to true.
  • allowFontScalingButtons (optional): Font scaling can cause troubles with high-resolution screens. You may want to disable it. Defaults to true.
  • currentPage (optional): a number to control the currently visible page from the parent. When this prop changes, the component scrolls to the given page. Useful for resetting to the first page when the user navigates back to the screen (see example below). Defaults to null (uncontrolled).
  • pageIndexCallback (optional): a function that receives the page index as a parameter on page change. Example Usage

Default Page Styles

For the pages in the pages array, you can set the default styles (and override the styles set by this component).

  • containerStyles (optional): override the default container styles.
  • imageContainerStyles (optional): override the default image container styles e.g. the paddingBottom of 60.
  • titleStyles (optional): override the default title styles.
  • subTitleStyles (optional): override the default subtitle styles.

Per-Page Navigation Conditions

For each page in the pages array, you can control whether the user is allowed to swipe or navigate forward/backward:

  • canSwipeForward (optional): a bool. When false, forward swiping is blocked and the Next, Done, and Skip buttons are disabled. Defaults to true.
  • canSwipeBackward (optional): a bool. When false, backward swiping is blocked. Defaults to true.

This is useful for requiring the user to complete an action (e.g. fill a form, accept terms) before proceeding. Update the pages array with new state to dynamically enable navigation:

<Onboarding
  pages={[
    {
      backgroundColor: '#fff',
      image: <Image source={require('./images/form.png')} />,
      title: 'Fill the form',
      subtitle: 'Complete all fields to continue',
      canSwipeForward: formIsValid,
    },
    ...
  ]}
/>

Note: the imperative goToPage() method is not affected by these conditions and can always navigate to any page.

Per-Page Button Labels

Each page can override the global button labels:

  • nextLabel (optional): a string OR a React-Native component. Overrides the global nextLabel for this page.
  • skipLabel (optional): a string OR a React-Native component. Overrides the global skipLabel for this page.
  • doneLabel (optional): a string OR a React-Native component. Overrides the global doneLabel for this page (applies on the last page).

Adjust Individual Page Styles

For each page in the pages array, you can override the default page styles. An example.

  • titleStyles (optional): modify styles of a specific page's title.
  • subTitleStyles (optional): modify styles of a specific page's subtitle.

Custom Components

You can provide your own custom components for the buttons and the dots. All of them have access to a isLight prop but it's up to you what you do with it. Also checkout this example.

  • SkipButtonComponent (optional): Skip Button, gets skipLabel as prop.
  • NextButtonComponent (optional): Next Button, gets nextLabel as prop.
  • DoneButtonComponent (optional): Done Button.
  • DotComponent (optional): Dot for the pagination, gets selected as prop to indicate the active page.

Custom Backgrounds

You can use any React element as a page background (e.g. a linear gradient) via the background prop. Pair it with isLight to control text/dot colors since the library can't auto-detect brightness from a gradient.

import LinearGradient from 'react-native-linear-gradient';

<Onboarding
  pages={[
    {
      background: (
        <LinearGradient
          colors={['#003c8f', '#5a9bf6']}
          style={{ flex: 1 }}
        />
      ),
      isLight: false,
      image: <Image source={require('./images/circle.png')} />,
      title: 'Gradient Page',
      subtitle: 'Using a custom background element',
    },
    {
      backgroundColor: '#e9bcbe',
      image: <Image source={require('./images/square.png')} />,
      title: 'Solid Color Page',
      subtitle: 'Still works the same as before',
    },
  ]}
/>

You can also combine both backgroundColor and background on the same page β€” the solid color provides smooth animated transitions while the gradient covers it visually.

Controlling the pages imperatively

You can control the Onboarding component imperatively with useRef.

const onboardingRef = useRef<Onboarding>(null);

<Onboarding
    ref={onboardingRef}
    pages={pages}
/>

onboardingRef.current.goNext()
onboardingRef.current.goToPage(2, true)
onboardingRef.current.goToPage(2, false)

Methods:

  • goNext() : Go to the next page.
  • goToPage(pageIndex, animated) : Go to the selected page.

Resetting the page on navigation

If you use a navigator (e.g. React Navigation) and want the onboarding to reset to the first page when the user comes back, use the currentPage prop:

import { useCallback, useState } from 'react';
import { useFocusEffect } from '@react-navigation/native';

const OnboardingScreen = () => {
  const [page, setPage] = useState(0);

  useFocusEffect(
    useCallback(() => {
      setPage(0);
    }, [])
  );

  return (
    <Onboarding
      currentPage={page}
      pageIndexCallback={setPage}
      pages={[...]}
    />
  );
};

TypeScript

Built-in TypeScript declarations are included. No additional @types package is needed.

Contributing

If you have a question, found a bug or want to propose a new feature, have a look at the issues page.

Pull requests are especially welcomed when they fix bugs or improve the code quality.

Releasing a new version

  1. Update the version in package.json.
  2. Add an entry to CHANGELOG.md with the new version number and a summary of changes.
  3. Commit: git commit -am "vX.Y.Z".
  4. Tag: git tag vX.Y.Z.
  5. Push: git push && git push --tags.
  6. Publish: npm publish.

Related Work

Acknowledgements

Built upon the work by Gosha Arinich which was originally inspired by AndroidOnboarder.

License

MIT.