I had been told by someone on here at one point (and I can’t find it now) that signups/logins should always be a backend workflow.
I can’t find any evidence or data that backs that idea up? I’ve looked at it from every angle. If privacy rules are set right, I don’t see a problem.
Can anyone tell me which is better and why?
Short answer…
In almost ALL normal use-cases, Sign Up and Login actions should be done from ‘page’ workflows.
Ok, thank you.
I appreciate your reply!
Was in a hurry and responded to another post…I need to slow down 
Login doesn’t make sense as a backend workflow.
For signup there are plenty of examples. Let’s say you have proprietary business logic or codes, you’d want to put it in a backend workflow.
Signup flow and signup action are different concepts. The sign up action may normally be done client side so it logs user in after creating the account, but if there is need to create separate data types, that flow or series of actions may be better done in backend.
Reason is, if you allow the extra actions of flow to take place backend, it doesn’t slow user down, as don’t need to wait for completion, and is therefore better UX. Also, anticipation of an Admin need to create accounts for other people, so user can create account using sign up action with backend taking over rest of flow, and admin using create account for somebody else with same backend workflow for remainder of flow.
I assume you’re talking about signing up another User (not the user themselves)?
Or are you actually referring to the user directly signing up themselves?
This.
Presumably then, you’re talking about something like a multi-factor auth signup process?
Or an Admin Approval process for new users? Something like that?
Or is there some other use case for this?
Thanks for the replies.
I’ve read so many older forum posts from years ago…and bookmarked a ton…but when I want to find something, it seems I never can find what I’m looking for. And sometimes using AI, things can go around and around in circles.
I have an older relative who takes a couple of medications each day. She was keeping track of the times she took them on paper. Yes, they have the plastic pill holders by day, and even some apps out there that do this…but she said those apps were too confusing.
So, I sat down and built her an app the other day that handles everything for her. She can set her meds, times, amounts, how often, etc. It has an easy onboarding process for older people. Then it alerts her when it’s time to take a med…she clicks a button, and it logs it. If she misses one, it alerts her, etc. Too many features to mention…but all so simple to use.
Then she said she had a couple of friends who could use this also.
The whole app is built using code and using Bubble as a backend using JS Globs, but since her friends want to use it, I added the auth page using Bubble.
They create an account with their phone number and a 4-digit PIN. Thought that was easier for older people.
When they log in, they can click forgot pin and they get a text, blah, blah, blah.
So, I had remembered reading somewhere that signup/login should be in the backend, but I couldn’t find where I had read it.
Thank you for all the replies
Added: When they create an account, they also get a text and can just click verify
Perhaps that temporary password generation should be in the backend?
Thanks.
Actually, the password (PIN in this case) is not temporary.
They get a text to verify their sign-up…they click verify and then can continue.
If they don’t click verify, the process stops.
So, actually, the only way a person can sign up with that number is if they have actual access to that phone.
Added: The user data type has a verified yes/no
