Gathering detailed insights and metrics for @apollosproject/ui-onboarding
Gathering detailed insights and metrics for @apollosproject/ui-onboarding
Gathering detailed insights and metrics for @apollosproject/ui-onboarding
Gathering detailed insights and metrics for @apollosproject/ui-onboarding
npm install @apollosproject/ui-onboarding
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (92.37%)
TypeScript (4.43%)
Objective-C (0.81%)
Java (0.75%)
Shell (0.51%)
Kotlin (0.41%)
Swift (0.38%)
Ruby (0.26%)
Starlark (0.07%)
C (0.01%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
NOASSERTION License
1 Stars
1,971 Commits
3 Watchers
1 Branches
15 Contributors
Updated on Nov 09, 2023
Latest Version
4.1.0
Package Id
@apollosproject/ui-onboarding@4.1.0
Unpacked Size
1.31 MB
Size
93.47 kB
File Count
96
NPM Version
lerna/4.0.0/node@v16.13.1+x64 (darwin)
Node Version
16.13.1
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
14
React Native components to create an Onboarding experience.
This package should be in your Apollo's Client if you got started with the example repo. For an example implmentation, check the apolloschurchapp
.
This package lets you configure onboarding in three different ways.
The "connected components" are built to work for the majority of use cases. They rely on an unmodified schema, but will probabbly work if you made additions or subtle changes.
To use these components, import them from the @apollosproject/ui-onboarding
package and compose them into the main slider.
import {
AskNotificationsConnected,
AskNameConnected,
FeaturesConnected,
AboutYouConnected,
LocationFinderConnected,
OnboardingSwiper,
} from '@apollosproject/ui-onboarding';
...
function Onboarding({ navigation }) {
return (
<OnboardingSwiper>
{({ swipeForward }) => (
<>
<AskNameConnected onPressPrimary={swipeForward} />
<FeaturesConnected
onPressPrimary={swipeForward}
BackgroundComponent={
<GradientOverlayImage source={'https://picsum.photos/640/640/?random'} />
}
/>
<AboutYouConnected
onPressPrimary={swipeForward}
BackgroundComponent={
<GradientOverlayImage source={'https://picsum.photos/640/640/?random'} />
}
/>
<LocationFinderConnected
onPressPrimary={swipeForward}
onNavigateToLocationFinder={() => {
navigation.navigate('Location', {
onFinished: swipeForward,
});
}}
BackgroundComponent={
<GradientOverlayImage source={'https://picsum.photos/640/640/?random'} />
}
/>
<ApolloConsumer>
{(client) => (
<AskNotificationsConnected
onPressPrimary={() => navigation.navigate('Home')}
onRequestPushPermissions={() =>
requestPushPermissions({ client })
}
primaryNavText={'Finish'}
BackgroundComponent={
<GradientOverlayImage source={'https://picsum.photos/640/640/?random'} />
}
/>
)}
</ApolloConsumer>
</>
)}
</OnboardingSwiper>
);
}
As you can see, each of the connected components may require specific props that may change depending on how your app is implemented. The notifications connected component right now is a little hairy, but that will be fixed in the future with a ui-notifications
package.
This is the best strategy if you wish to change the schema or mutations for your components, but don't want to change the way the components look or function.
The aproach is roughly the same as above, but you will have to define your connected
components locally. You can import the underlying visual components from the ui-onboarding
package by importing without Connected
. IE: import { ConnectedAskName } ...
becomes import { AskName } ...
.
This is the most advanced implementation, but gives the most control. You can import the <Slide>
component (whose props are documented in PropTypes) to construct your very own slide. You can look at the slides defined in this package for reference on how to construct a custom slide.
No props are needed. The first and only child should be a callback function which is called passing the arg ({ swipeForward })
. Calling swipe forward imperatively will move the onboarding slider forward by one slide. The callback function should return
A. A React.Fragment
with each slide node
as a child.
B. An array of slide nodes
.
Looking for more flexibility? Want to jump to a specific slide or swipe back. Checkout the scrollBy
arg.
Using this package automatically provides analytics over the onboarding experience, assuming you areusing the @apollosproject/ui-analytics
package.
As of right now, each screen emits a "ScreenName Completed" or "ScreenName Skipped" event when the screen has been completed or skipped. We consider this an "80 for the 20" aproach, because it is enough information to construct a funnel chart display points at which a user drops off from the Onboarding flow.
If further analytics events are required, submit an RFC (or a pull-request!) with what you are looking for, and our team will take a look.
You can implement your own anlytics by passing a pressPrimaryEventName
or pressSecondaryEventName
prop to the Screen
component. If those strings are passed, a track
will be called when the primary or secondary button is pressed.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
binaries present in source code
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no SAST tool detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
project is not fuzzed
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
129 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More