Login (signup)

[jamalsoueidan]

I don't see anything related to sign up on the login page, I know that you just need to type email and you get an password and you get to go as new customer.

But you have tested this out if it make any sense for new customers?

Because for most users they are used to go to sign up, and I wonder if they will understand that login means also sign up!

[osseonews]

Yeah, I agree. Customers won't know what the heck is going on. This is my main reluctance to using hydrogen or shopify headless and why I may just go back to Liquid, very reluctantly. The Customer Account login is very poorly designed from a user perspective. I don't know of any other website that has a login flow like this. It is just very confusing to most users and I can't imagine it converts well at all. Shocking that Shopify doesn't realize this, as Shopify usually is spot on with UI/UX.

[jamalsoueidan]

I think the problem is that they are not being given enough time to work on these features, or there are too few people involved.

Regarding the Customer Account API, the feature that allows users to stay logged in throughout the checkout process is not functioning. They have removed the email and phone fields, preventing users from updating this information while logged in, if a user needs to change their phone number, they must call customer service, which increases our workload. I don't know if login is supported by other languages beside english.

The Vite HMR is broken; it seems to have been tested only with native elements. Since last Friday, there has been no response about this issue.

[osseonews]

Yeah, fact of the matter is that building a headless platform on React for ecommerce is extremely difficult. I can't imagine the team has an easy job here and you might be right that the team Shopify has put on this is too small for the massive amount of work it entails. I've been working on headless for 4 years nearly every day, and it's a constant struggle because of much of the ecosystem is just all over the place. But, having done this for years, it's very strange how they are approaching Customer Account API and some other features for Remix/Hydrogen, and they seem to be creating a situation that will greatly slow the adoption of Remix/Hydrogen in favor of just using Liquid and programming apps in Remix. I mean Remix already has some good options for Auth, so why can't they just integrate with those? I did notice that even on Liquid they allow the new Customer Accounts set up, but I'm willing to be they have very few if any customers using this in a Liquid theme because the UI is just terrible. The Customer Accounts API is obviously designed primarily for headless implementations. But I can't see how it can be used effectively in a headless set up. Unfortunately, I have spent months now developing my headless shopify store, and so might just have to go with it. Really struggling, though with a decision here.

[Lachie-Young]

I'm willing to bet that Shopify is hesitant to allow headless storefronts to deal with end user passwords so they've had to settle for a subpar UX...

[osseonews]

Headless platforms don't ever deal with passwords, even when they implement username/password login. The password is not stored on the headless site. It still is sent to the provider, like Shopify. So I don't see this as the motivator here. There are no security concerns. Shopify went with this new customer login because they are 100% correct in that most people are tired of passwords and sending a code is easier for everyone. However, the problem is that we are probably years away from this becoming a standard, so most people still expect a choice of signin options. In fact, logging in with Social Auth, like Google, is now incredibly popular, even more so than a code, but Shopify doesn't offer it on headless and on Liquid you need to pay for some third-party app to offer social auth? Even if you just offer login with a code, you need to have a decent UX/UI so the user understands what is going on. But the Shopify implementation is just terribly confusing to the user. The primary issues now are that you can't send a user to Shopify.com to login so they need to offer a possibility for a subdomain for the sign in, and second, they need to offer an ability to add text on the sign in page to explain to the user how this works. Finally, they need to offer social auth. It is crazy that you need to pay another monthly fee for this. Social auth is crucial for headless.

[jamalsoueidan]

Agree with @osseonews
It's confusing.

Right now I can only ask people to login, but if new users come to my shop, they dont understand where is the sign up page? and beside that the login page is not translated to arabic, one of the most spoken languages in the world.

[jamalsoueidan]

@wizardlyhel What is your thought? Are we getting signup link, or maybe change the text on the page to explain it's both login and signup? and do you know how to translate the text? Since my store is in Danish?

[wizardlyhel]

For changing the language of the login page, pass LanguageCode DA to customerAccount.login()

context.customerAccount.login({
    uiLocales: 'DA',
})

Here is a list of supported languages https://shopify.dev/docs/api/customer#authorization-propertydetail-uilocales

As for the sign up link, Hydrogen team don't have much information either. I will forward these feedbacks to the customer accounts team.

[jamalsoueidan]

We need arabic language @wizardlyhel how do we get this? Is it possible to provide the translation?

[wizardlyhel]

We are working on bringing more language options to the new customer account. However, there is no timeline we can provide. This isn't a surface area where dev can supply translation to solve this problem.

[jamalsoueidan]

Who should I contact to ask for deadline?

[joehannouch]

So I understand that there is no way to offer a login/sign up page (username/email with password) on Hydrogen/Headless storefronts?

[jamalsoueidan]

If you are using the old customer account api, you can still do that.