Technology
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
[email protected]
[email protected]
Icon attribution | Banner attribution
view the rest of the comments
I've been an android developer for a decade at this point, I'm aware of how app deep links work.
The comparison is not "what LOE is call linking from scratch" but rather "how does call linking meshing into existing production codebases across all platforms compare in LOE to 3 buttons?" And the answer is self evidently more.
You're minimizing the amount of effort and we're comparing it to buttons. Adding "a few buttons" is very different than setting up 3 platforms to all use a new protocol (calls from links will require new handling - previously all calls were just based on authenticated users being allowed into webrtc calls based on their tokens. Now you have to have a new handler which joins a call with the token in the URL - that can't be handled identically). Then we get into the Android app, much of which is still in Java, which uses multi-activity-srchitrcgure meaning you've gotta pass data through each layer manually, rewriting each of these activities to accept the new deep link and route to the right end.
And then you've got to be sure it all coordinates across iOS, Android and your backend.
It's not hard but it's not "a few buttons". It's probably 2 weeks of work for skilled and competent engineers, 1 per platform.
Do you actually have any experience in Mobile dev? You sound like a fresh outta college junior eng - cocky and confident that everyone else is wrong, making it harder than it needs to be etc.
Just like that cocky junior eng you're too unaware of what you don't know to realize you're wrong. Wade through the grass a few times and you'll realize the flowery meadow is full of snakes.
You're barking up the wrong tree here, buddy. I'm not the person who said "it's a few buttons."
I was merely pointing out that from a conceptual standpoint, deep links don't need months of research and design work. The difficulty—as you pointed out—comes in knowing how to work with the various different platforms and integrating the feature into existing codebases.