Hi there,
I am looking for some advice regarding my new app build.
The App is complete as of yesterday.
But I do have some questions regarding the onboarding / registration steps, and how they are currently working.
Ultimately, this is the concept. I have built the App for two purposes:
- Providing pet owners resources to care for their pet (signed in users). Adding their information / pet information / medical information / calendar resources to log appointments + upcoming trips / key contacts and support for their pets. Sort of like a smart hub for pets.
- The second functionality works hand in hand as the “PublicURL”. Basically, I am selling custom pet tags with individual QR codes attached. I have created a tab (public viewing) linked to the specific pet, so if the pet were to go missing, the member of the public could scan the QR code → land on the PublicURL page and have direct access to the owners information (phone / email), as well as the pets identification information.
The PublicURL also has the functionality that for people caring for a pet (pet sitter / boarding kennel staff) can scan the QR code on the pets tag, and they will have access to the pets information / pet medical history / any documentation that the owner has uploaded in the app.
Okay, so now for my questions (I am new to the app building world), and I am struggling to replicate what a “new user” would experience, and cannot work out if i have set this up correctly.
I need to confirm firstly - how to confirm the URL is that directly links to the User Registration Tab. I believe I have set up the visibility rules correctly, but unsure. Can anyone confirm exactly what visibility rules should be linked?
The ideal flow → a sale is made on my store, the owner is emailed a link to the Registration Tab (where they register their information / pet information etc) and have access to the app features.
The tag is simultaneously created and printed with a Print on demand company. I need to confirm that the URL (linked to the QR tags) land users on the PUBLICURL tab.
My third question is in relation to the Onboarding Flow - currently, the new user will click the link to the USER REGISTRATION, once complete, they will then flow onto the GET STARTED TOUR (a seperate tab). Currently I don’t think this flow is working, and I’m not sure how to fix it. Any suggestions on where to check in my settings?
Also with all of this information, what settings should i have set for the App Access? Access (Public) / Users (Anyone)?
on confirming the url to user registration
so first, you wanna kno the url that sends someone direct to the registration part
most “modern” app builders (like glide) don’t give you a link to a tab per-se, but, to a screen based on what is visible for the current user
so think:
- the real link experience for somebody not signed in
- what do they see first? usually: sign in/registration
- “visibility rules” are basically what decides who can see which screen/tab
the visibility rule for a registration tab should look something like:
- only show this tab if [user is not signed in] or [user profile is not setup]
that means
- if a public, not-logged-in human hits your app url, they see registration
- if an owner is already signed in and setup, they won’t see the registration anymore
so, check your tab visibility settings:
- open your registration tab in glide
- make sure visibility says: “when user profile is empty” or “when signed in user’s email is empty”
- or use a boolean, like “show registration if profileComplete is false”
linking from store purchase
when you sell a pet tag, you’re sending the owner a link.
- this should be your “main app url”, but ideally, a deeplink to the registration (if possible)
- glide doesn’t generate special links for tabs, but, if registration is visible for NEW USERS and invisible for profile complete, the base app url will “land” them there anyway
- test: open your app in an incognito window, and see what screen you get. (pretend you’re a brand new hooman)
if it brings you to the registration form → you’re good. if not, adjust those visibility rulez
qr tag and public url
for the physical tag, the qr code must send ppl to a specific pet’s “public page” in your app
requirements:
- you need a unique public url (ideally) for each pet
- glide let’s you generate a “row link” or “deep link” per row in a table
- this takes work: for each tag order, you have to “assign” the right pet, generate their public url, and send that to your tag printer for the QR code
- test this: scan the qr code (or pretend by copying the public url), and confirm you’re seeing the right pet’s info without logging in
- again: the public page needs “visibility: public”
onboarding flow
“user registers, but doesn’t get automatically sent to the get started tour”
glide and many platforms don’t have a “step by step force” unless you build custom actions or conditions
suggestions:
- after registration, create a button or automatic action that links to “get started”
- optionally: set a value on profile like “completed registration”, and only show the get started tab if not completed tour
- if you’re not seeing this work, double check:
- does your registration finish with a “done” button that points people to the get started tour?
- are the visibility rules on “get started” correct (maybe only show if registration complete, etc)?
- you can debug by signing in as a new test user, and seeing each flow point
- settings for this stuff often in the action/flow tied to registration completion (or by tab visibility rules)
app access setting
“should i use app access (public / anyone)?”
- if you want lost pets & their info to be viewable without ANY login: set to Public
- if you only want owners/pet sitters to see: restrict to “public with email” or “users: invited only”
- but for your case, public makes sense, as long as sensitive info is controlled by visibility on the pet’s public page (eg, you don’t show sensitive medical unless needed)
1 Like