There are a number of options to consider depending on context and goals you would like to achieve. Help should be provided when needed, in the right time and right place. Other than that help content should be largely be out of users way until requested. I will address each point briefly without getting into interaction design patterns, hopefully that would be of help:
Onboarding : Help delivered at this stage is meant to introduce users to the app features and functionality. The main purpose being to reduce the learning curve. A good example here is guided tours.
Contextual help: this type of help is inseparable from the core content and is generally a reflection of best practices applied to labelling and navigation. Contextual help relies on providing users with good information scent as to what they can do and where they can go next.
Adaptive help: this type of help is provided to users based on where they are in the user journey. Facebook and google analytics incorporate this type of help via dedicated search box. The main purpose behind adaptive help is to increase help content relevancy, reduce clutter, provide help content when needed and ultimately keeping users in control.
Last but not least, there is dedicated help which generally takes the form of a dedicated help section that houses frequently Asked questions and help articles. While this is really a great option to have depending on the need, it does come at a price as it’s not contextual. The main purpose here is to cope with complexity and to house help content in a central location.
Now, to answer your question, consider carefully what type of help you need and why and explore options to reduce the need for help.
Generally speaking contextual help is the most relevant here along with on boarding tutorial if the need arises. Testing with your users should hopefully help you decide on the best option to take.