@[email protected] to [email protected] • 8 months agoWhat the actual fuck?!lemmy.worldimagemessage-square42fedilinkarrow-up1277arrow-down112file-text
arrow-up1265arrow-down1imageWhat the actual fuck?!lemmy.world@[email protected] to [email protected] • 8 months agomessage-square42fedilinkfile-text
minus-square@[email protected]linkfedilink5•8 months agoNot really. Android apps can declare which urls they accept as deep links. Once that is registered with the system (ie after install) then links of that type can be opened by the app. It doesn’t have to match the package name.
minus-square@taladarlink-1•8 months agoThe package name should, however, match a domain owned by the publisher of the package.
minus-square@taladarlink5•8 months agoThat is how Java names work. The whole domain-like appearance is meant to avoid name collisions between packages made by different companies.
minus-square@taladarlink4•8 months agoYou are thinking of the standard library, I mean package names for third party code, specifically for what Java calls packages. https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
Not really.
Android apps can declare which urls they accept as deep links. Once that is registered with the system (ie after install) then links of that type can be opened by the app. It doesn’t have to match the package name.
The package name should, however, match a domain owned by the publisher of the package.
deleted by creator
That is how Java names work. The whole domain-like appearance is meant to avoid name collisions between packages made by different companies.
deleted by creator
You are thinking of the standard library, I mean package names for third party code, specifically for what Java calls packages.
https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html