Start to finish such a helpful guide. I planned on using this feature not only during on-boarding but other no standard pages. Also helping solidify my understanding of custom states. Thank you!!
@gaby I came back to this video because I need to do something similar. Of course, I need to add a little complexity to it and have a couple of questions for you:-). 1) How would this change if you have multiple pages in your app that need to be introduced to the new user? 2) Demo data. In the video's app, it's full of data. My app is multi-tenet and data is constrained by company (users belong to companies). I would like to have some dummy data in the app so that a user's experience isn't completely blank on every sign-up. If you were in my shoes, how would you supply demo data so that there's something there instead of nothingness when brand new users register for the first time and you want to show them around? Remember, I have multiple individual companies using my app with privacy rules. Is there a programmatic way to do it or is this a manual process? Thanks:-)
Hello, I have a question. I see that for this tutorial you a using an index page. In my use case when the user signs up. The workflow take them from the index page to the profile page to create their profile. So of course when try to Set a State in the workflow from sign up to the profile page the 'Group Onboard' isn't available in the elements. How do I remedy this?
You can pass the state's value to the other page via URL parameter. Extract the parameter on the second page and save it to a new custom state there. Custom states are page-level only, so hopefully that clears things up. Check out this tutorial for how to use URL parameters: ua-cam.com/video/vLHiC4Iq8u0/v-deo.html
@@coachingnocodeapps Hey, I was having this issue. I checked the app-wide search video, there when a button 'go' is clicked that is when you are passing the URL parameter to another page. But here, nothing is getting clicked as such before the group onboard becomes visible. I mean, the onboarding starts as soon as the user signs up, which is happening on another page. So how to go about this?
Thanks for the suggestion! In general, it's a repeating group of Activity Events. Every time something happens in the app, a new Activity Event gets created, and depending on the Event's relationship to the user, it will show up in this RG (based on constraints). The category color icon uses a condition to change color based on a "Type" field under the Event data type.
The terms being used might be a bit confusing. Let me back up... this app could have several data types: Payment, Contact, Performance Event, Activity Log. Since an RG can only display a list for 1 of those types, you want one of your data types to act as a "common ground", which is what "Activity Log" does. Every time a Payment is created, a new Activity Log is created (type = Payment, Description = $100 Reservation for 2 people). Every time a Contact is edited, a new Activity Log is created (type = Contact, Description = Sally Jones has a new phone number), and so on. So the RG displays these Activity Logs, which are generated every time anything else happens in your app.
That's the way this demo app is set up, yes. But it's really up to how you want your activity feed to work. You can create an Activity Log when a user logs in or when a database change is made - doesn't necessarily need to happen every time something else is created.
Hi, question: is there any way we can create this onboarding AND let the user interact with just some elements? I mean, I dont want him to interact with the full page, but I dont want him to be blocked from taking an action that I actually want him to take. Any ideas? The onboard as shown above is ust informative, not actionable, right? (not that its not amazing, its veeery usefull... just thinking further here...).
Hi Felipe, great question! If you want to allow for some interactivity, then you can have those clickable elements within the main onboarding group (that overlays the rest of the page). That way those items are still accessible. Easiest way might be to create duplicate elements to copy into the onboarding group so that you're not messing with the "real" versions behind the onboarding group. Hope that makes sense!
Alternatively, you could probably use 3 or 4 group elements to mask everything but the element you wish to keep clickable... Then, if they press it, you could include a "Return to walk through" button to bring the user back to the walkthrough at the point they exited.
Start to finish such a helpful guide. I planned on using this feature not only during on-boarding but other no standard pages. Also helping solidify my understanding of custom states.
Thank you!!
I'm glad it was helpful, Paul!
One of your best videos yet!
@gaby I came back to this video because I need to do something similar. Of course, I need to add a little complexity to it and have a couple of questions for you:-). 1) How would this change if you have multiple pages in your app that need to be introduced to the new user? 2) Demo data. In the video's app, it's full of data. My app is multi-tenet and data is constrained by company (users belong to companies). I would like to have some dummy data in the app so that a user's experience isn't completely blank on every sign-up. If you were in my shoes, how would you supply demo data so that there's something there instead of nothingness when brand new users register for the first time and you want to show them around? Remember, I have multiple individual companies using my app with privacy rules. Is there a programmatic way to do it or is this a manual process? Thanks:-)
Good one. Thanks.
Glad you liked it!
Hello, I have a question. I see that for this tutorial you a using an index page. In my use case when the user signs up. The workflow take them from the index page to the profile page to create their profile. So of course when try to Set a State in the workflow from sign up to the profile page the 'Group Onboard' isn't available in the elements. How do I remedy this?
You can pass the state's value to the other page via URL parameter. Extract the parameter on the second page and save it to a new custom state there. Custom states are page-level only, so hopefully that clears things up. Check out this tutorial for how to use URL parameters: ua-cam.com/video/vLHiC4Iq8u0/v-deo.html
@@coachingnocodeapps Hey, I was having this issue. I checked the app-wide search video, there when a button 'go' is clicked that is when you are passing the URL parameter to another page. But here, nothing is getting clicked as such before the group onboard becomes visible. I mean, the onboarding starts as soon as the user signs up, which is happening on another page. So how to go about this?
Is this still possible with the responsive engine?
você conseguiu deixar responsivo?
Awesomeness!!!! Lesko!
I hope it was helpful!!
I would like to see a short tutorial or guide on how you made the activity feed in this template.
Thanks for the suggestion! In general, it's a repeating group of Activity Events. Every time something happens in the app, a new Activity Event gets created, and depending on the Event's relationship to the user, it will show up in this RG (based on constraints). The category color icon uses a condition to change color based on a "Type" field under the Event data type.
So are you saying when an event is created it also creates an activity. Or does the RG bring all three types of data into one.
The terms being used might be a bit confusing. Let me back up... this app could have several data types: Payment, Contact, Performance Event, Activity Log. Since an RG can only display a list for 1 of those types, you want one of your data types to act as a "common ground", which is what "Activity Log" does. Every time a Payment is created, a new Activity Log is created (type = Payment, Description = $100 Reservation for 2 people). Every time a Contact is edited, a new Activity Log is created (type = Contact, Description = Sally Jones has a new phone number), and so on. So the RG displays these Activity Logs, which are generated every time anything else happens in your app.
Ok, if understand it right it creates 2 different things every time. Like the payment thing and the activity thing.
That's the way this demo app is set up, yes. But it's really up to how you want your activity feed to work. You can create an Activity Log when a user logs in or when a database change is made - doesn't necessarily need to happen every time something else is created.
thank you
You're very welcome!
How did you make the day/night skin?
Hey there! You can check out our template for that in the marketplace!
Hi, question: is there any way we can create this onboarding AND let the user interact with just some elements? I mean, I dont want him to interact with the full page, but I dont want him to be blocked from taking an action that I actually want him to take. Any ideas? The onboard as shown above is ust informative, not actionable, right? (not that its not amazing, its veeery usefull... just thinking further here...).
Hi Felipe, great question! If you want to allow for some interactivity, then you can have those clickable elements within the main onboarding group (that overlays the rest of the page). That way those items are still accessible. Easiest way might be to create duplicate elements to copy into the onboarding group so that you're not messing with the "real" versions behind the onboarding group. Hope that makes sense!
Alternatively, you could probably use 3 or 4 group elements to mask everything but the element you wish to keep clickable... Then, if they press it, you could include a "Return to walk through" button to bring the user back to the walkthrough at the point they exited.
Gaby how do I get night and day mode
midna the Ferret Gla Hi! The link to the template is in the description above :)