Feature Request: Client Chooser Landing Page
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
As the ability to craft links to open locally installed apps exists (nextcloudtalk://), we are now missing some sort of web landing page as many other vendors provide today; see example screenshots:
… where the user is able to decide to join using their browser (aka web-experience) or dependent of the current connecting platform (talk clients exists for win/mac/linux/ios/android) to start the equivalent app by offering a dynamic crafted protocol handler url nextcloudtalk://open-conversation to start the locally installed app instead.
Talk on iOS for example does support the following parameters, some are given in the URL {server}/{withRoomToken} while others like {user} are known by the browser -> _last_logged_in_user:
server: The Nextcloud Server URL
user: Your UserID, used for an account on server, that is logged into the Talk App
withUser: The UserID of the user you want to talk to
withRoomToken: The room token of an existing room on server
Usage:
nextcloudtalk://open-conversation?server={serverURL}&user={userId}&withRoomToken={roomToken}
What do you think ?
Originally posted by @LexioJ in https://github.com/nextcloud/talk-ios/issues/671#issuecomment-2506856381
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Start by reviewing the existing nextcloudtalk:// link behavior and the listed server, user, and room-token parameters across the supported Talk clients. Done would be a landing page that lets users choose the browser experience or an appropriate installed app while preserving those parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100