Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement new shorter universal links #10083

Closed
jakubgs opened this issue Feb 26, 2020 · 13 comments · Fixed by #10222
Closed

Implement new shorter universal links #10083

jakubgs opened this issue Feb 26, 2020 · 13 comments · Fixed by #10222
Assignees
Labels
feature feature requests

Comments

@jakubgs
Copy link
Member

jakubgs commented Feb 26, 2020

Feature Issue

The current form of links is too verbose and long. After discussing this with @jarradh and some others we've decided to use shorter forms, like so:

These were implemented in status-im/universal-links-handler#29 and are already deployed.

User Story

As a user, I want to shorter universal links so that it's easier to remember them and make them yourself. They also produce more readable QR codes.

Description

We will have to support both the old and the new way for at least one release to not break the old links. After that we can see in server logs how many people still use them and we can retire them eventually in a later release to avoid maintaining dead code.

Acceptance Criteria

New forms of universal links are supported on Android and iOS, in addition to old forms.

@jakubgs
Copy link
Member Author

jakubgs commented Mar 6, 2020

@hesterbruikman can we include this for 1.2? As 1.1 appears to be already taking shape.

@hesterbruikman
Copy link
Contributor

I think that's fine, as long as we have it by the end of this month. As I understand it, this isn't hugely complex or would risk any delays. Added v1.2 release label.

Does this issue require any updates in https://github.com/status-im/universal-links-handler/?

@jakubgs
Copy link
Member Author

jakubgs commented Mar 6, 2020

The necessary changes have already been made in status-im/universal-links-handler#29 and deployed.

@hesterbruikman
Copy link
Contributor

Then I'm confused 🙂 Are you saying it's not in the release cut for V1.1?

@jakubgs
Copy link
Member Author

jakubgs commented Mar 6, 2020

It's very simple. There are two parts to this:

In order to change the structure of links under https://join.status.im/ two changes have to be made:

On a specific example. If you go to https://join.status.im/@jakubgs.eth - which is the new form of https://join.status.im/user/jakubgs.eth - it will display a page, but it will not work with the App, regardless of from where you open it. For that to work changes have to be made to status-react.

@jakubgs
Copy link
Member Author

jakubgs commented Mar 6, 2020

But there is still the issue of #10029 and #10017 which touch partially on the same thing.

I think QR codes should always use full URLs and never use shorter forms like status-im://jakubgs or @jakubgs because this way they will work for anyone, not just for people who have the app installed.

@hesterbruikman
Copy link
Contributor

Thanks for explaining!

I think QR codes should always use full URLs and never use shorter forms like status-im://jakubgs or @jakubgs because this way they will work for anyone, not just for people who have the app installed.

Agree! I hate it when the short form doesn't work and I also get zero information about what it's trying to do

@hesterbruikman
Copy link
Contributor

Btw @jakubgs do you know why exactly we don't allow upper case, spaces, etc? I see a lot of value in being able to create a channel anywhere, just by editing a url. The format restrictions limit that feature.

Nothing concrete yet, but thinking of how we can offer a 'create and share channel' feature on status.im

@jakubgs
Copy link
Member Author

jakubgs commented Mar 9, 2020

I don't know exactly why, but it makes sense to me. Look at Twitter, hashtags can't have spaces or special characters either. I think it's sensible. And you still can "create" a channel by just writing down a URL like https://join.status.im/my-new-channel just that if you for example use uppercase it will not work: https://join.status.im/My-New-Channel

What we could possibly do is simply redirect the upper case URL to the lower case URL.

@hesterbruikman
Copy link
Contributor

What we could possibly do is simply redirect the upper case URL to the lower case URL.

That would solve it. What I noticed before was the issue of having #friendschat when using Join Chat in Status (validation permits uppercase) and #Friendschat when using the url https://join.status.im/Friendschat. They'd open 2 different channels.

@jakubgs
Copy link
Member Author

jakubgs commented Mar 9, 2020

There you go: status-im/universal-links-handler#32

@jakubgs
Copy link
Member Author

jakubgs commented Mar 24, 2020

#5302 is old but still relevant. We should fix the deep linking of upper case channel names.

@jakubgs
Copy link
Member Author

jakubgs commented Apr 1, 2020

Due to issues found in #10222 I had to replace /@ format with /u/ because iOS eats the @.
Related change: status-im/universal-links-handler#35

Fuck Apple.

cammellos added a commit that referenced this issue Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature feature requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants