Tips and Tricks for TipKit

My designers like TipKit, especially the newer flavor we can control the content.

What are some best practices or tips and tricks to share with product owners when designing around what the framework is capable of doing?

Concepts that might be relevant:

  • Onboarding
  • FAQ
  • Progressive disclosure of new features
  • HELP / support workflows
Answered by Frameworks Engineer in 892865022

TipKit has some useful APIs for not overwhelming users the first time they launch your app.

For general features that you want all users to know about I'd recommend setting displayFrequency as part of your Tips.configure call. That will space the presentation of tips out so your users don't have to tap through all of them before using your app. I'd also recommend trying to use the inline TipView where possible as it won't overlay your app's existing UI and allows users to interact with it when they are ready.

It can be useful to set #Rules for your advanced features so they are only displayed to users that will benefit from them. Eg. For something like a media player app with a tip about customizing the subtitle font or color, you could set a rule that only displays that tip to users that have subtitles enabled.

TipGroup is a great API for the progressive disclosure of features. It can be customized to show tips in a specific order for features that are related to one another. It also works great in conjunction with #Rules and displayFrequency

Also, make sure to call invalidate on your tips when the features they describe are used. That way users will not see tips about features they have already discovered!

Thank you! Hopefully this helps!

Accepted Answer

TipKit has some useful APIs for not overwhelming users the first time they launch your app.

For general features that you want all users to know about I'd recommend setting displayFrequency as part of your Tips.configure call. That will space the presentation of tips out so your users don't have to tap through all of them before using your app. I'd also recommend trying to use the inline TipView where possible as it won't overlay your app's existing UI and allows users to interact with it when they are ready.

It can be useful to set #Rules for your advanced features so they are only displayed to users that will benefit from them. Eg. For something like a media player app with a tip about customizing the subtitle font or color, you could set a rule that only displays that tip to users that have subtitles enabled.

TipGroup is a great API for the progressive disclosure of features. It can be customized to show tips in a specific order for features that are related to one another. It also works great in conjunction with #Rules and displayFrequency

Also, make sure to call invalidate on your tips when the features they describe are used. That way users will not see tips about features they have already discovered!

Thank you! Hopefully this helps!

Tips and Tricks for TipKit
 
 
Q