# What is the best logic for my new user / client?

**URL:** <https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323>\
**Category:** Ask for Help\
**Created:** [January 4, 2023, 2:02pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323 "2023-01-04T14:02:10Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![erwblo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/erwblo/32/75_2.png) [@erwblo](https://community.glideapps.com/u/erwblo)\
**Post date:** [January 4, 2023, 2:02pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/1 "2023-01-04T14:02:10Z")

</div>

OK, this is what I have: an online shop where people can look around but need an account plus some filled-in extra personal data fields before they can buy something. What is the best way of onboarding and how to achieve that?  
Right now I have three buttons:

> 1. Sign In / Sign Up, visible when not logged in or when not signed up, leading to sign in page.
> 2. Finish Profile, visible when fields like name and address are empty, leading to edit screen page with personal data fields
> 3. Buy, visible when signed in and profile page completed, leading to form screen page, with info about product, amount etc.

I realize that’s too much. For all people this should be 1 flow, I think, but what would that look like in a custom action? What would the custom action for a new user look like? Which automatic steps follow each other? And don’t say 1,2,3 😉 because that’s not the way things seem to work.

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 2:19pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/2 "2023-01-04T14:19:01Z")

</div>

This is tough. In my experience, getting them to a sign-up screen is hard enough.

I once held that I should _only_ show the onboarding screen until they had finished the profile, but the abandonment rate was horrible. Only after I allowed them in to get a “sneak peek” was I able to get them to finish the profile. The key was to put a link to the profile on every screen until it was filled in. What your definition of completely filled in will differ, of course. I _allowed_ them to put in a phone number, for example, but that was not required as part of a completed profile. EMAIL was required.

I should add this particular app had nothing to buy. Information only.

Does your App have things they are not able to purchase elsewhere? If so, that’s an added ‘pull’.

---

<div class="post-metadata">

**Author:** ![erwblo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/erwblo/32/75_2.png) [@erwblo](https://community.glideapps.com/u/erwblo)\
**Post date:** [January 4, 2023, 2:24pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/3 "2023-01-04T14:24:15Z")

</div>

Yeah, this is totally unique (no competitor due to unique competitive advantage) and everyone can look around and see everything and all that before buying but after that, I still think I need to remove every unnecessary step.

So the problem is not loosing clients, the question is how do I make things as easy and logic as possible for them.

And besides that, I want to learn to use this better too (haven’t learned a thing so far today @Darren_Murphy 😉 )

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 4, 2023, 2:44pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/4 "2023-01-04T14:44:57Z")

</div>

Didn’t we already have this discussion a few days ago? 🤔

I already gave my recommendation:

> [@How to do this more simple? (Signing up with required extra data fields)](https://community.glideapps.com/t/how-to-do-this-more-simple-signing-up-with-required-extra-data-fields/56082/4):
>
> That sounds perfectly fine to me slight_smile I guess if you wanted to “tease” your users a bit, you could make the buy button available immediately after they’ve signed up, but put a conditional action on it. If their profile is completed, let them go ahead with the purchase. But if it isn’t, tell them they have to complete their profile first, and send them to their profile edit screen. It really depends on the user experience that you want.

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 2:57pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/5 "2023-01-04T14:57:18Z")

</div>

> [@How to do this more simple? (Signing up with required extra data fields)](https://community.glideapps.com/t/how-to-do-this-more-simple-signing-up-with-required-extra-data-fields/56082/4):
>
> “tease” your users a bit

Perfect answer!

---

<div class="post-metadata">

**Author:** ![erwblo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/erwblo/32/75_2.png) [@erwblo](https://community.glideapps.com/u/erwblo)\
**Post date:** [January 4, 2023, 2:59pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/6 "2023-01-04T14:59:16Z")

</div>

My question is not so much the logic, I know the steps that I need them to take, and I have that up and running, but I wonder if there is a better way. A shorter way. Is it possible to lead them from 1 to 2 to 3 with a custom action? Or is that not possible? So after they signed up, show them the edit profile screen, and after finishing the profile, show them the buy form. As automation.

Like this:

![CleanShot 2023-01-04 at 16.03.09@2x](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/9/e9c87d245410335b20712f67bc7c5d5b8fda022f.png)

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 4, 2023, 3:05pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/7 "2023-01-04T15:05:02Z")

</div>

> [@erwblo](#):
>
> So after they signed up, show them the edit profile screen

I think @Darren_Murphy’s solution not only makes sense but is pretty common in the ‘checkout’ scenarios on websites. Only after you fill up your cart and are ready to purchase to they ask you all the pertinent information (which may have changed since last time anyway).

---

<div class="post-metadata">

**Author:** ![erwblo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/erwblo/32/75_2.png) [@erwblo](https://community.glideapps.com/u/erwblo)\
**Post date:** [January 4, 2023, 3:11pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/8 "2023-01-04T15:11:05Z")

</div>

I am trying to understand some of the logic behind Glide as well 😉  
So this is not an option, right?  
 ![CleanShot 2023-01-04 at 16.03.09@2x](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/9/e9c87d245410335b20712f67bc7c5d5b8fda022f.png)

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 4, 2023, 3:16pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/9 "2023-01-04T15:16:52Z")

</div>

Well, you can do that, but what you’ll most likely end up with is a Form Screen on top of an Edit Screen on top of the Sign In Screen.

The thing is, you can’t set up an action to stop and wait for a user to do something. What you need to do is create a flow. So you show the first screen, and then stop and wait for the user. Once they’ve done something, you check what they did and move on to the next step. And so on…

---

<div class="post-metadata">

**Author:** ![erwblo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/erwblo/32/75_2.png) [@erwblo](https://community.glideapps.com/u/erwblo)\
**Post date:** [January 4, 2023, 3:19pm UTC](https://community.glideapps.com/t/what-is-the-best-logic-for-my-new-user-client/56323/10 "2023-01-04T15:19:06Z")

</div>

> [@Darren\_Murphy](#):
>
> The thing is, you can’t set up an action to stop and wait for a user to do something.

Ah ok! Clear! And thanks, maybe it was a stupid question, but I learned what is not possible!
