fastandcurious@lemmy.world to Privacy@lemmy.ml · 1 year agoWhat the actual fuck?!lemmy.worldimagemessage-square38fedilinkarrow-up1256arrow-down111file-text
arrow-up1245arrow-down1imageWhat the actual fuck?!lemmy.worldfastandcurious@lemmy.world to Privacy@lemmy.ml · 1 year agomessage-square38fedilinkfile-text
minus-squaretanja@lemmy.blahaj.zonelinkfedilinkarrow-up6arrow-down5·1 year agoTheir website is slickapp.co (without the m at the end), but their Android package name is com.slickapp. Isn’t that a bit of an issue? For example, when handling URLs?
minus-squarebiscat@lemmy.worldlinkfedilinkarrow-up15·1 year agoDon’t most Android packages begin with com. ?
minus-squareSkull giver@popplesburger.hilciferous.nllinkfedilinkarrow-up11·edit-21 year ago[This comment has been deleted by an automated system]
minus-squarehuginn@feddit.itlinkfedilinkarrow-up5arrow-down1·1 year 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.
Their website is slickapp.co (without the m at the end), but their Android package name is com.slickapp.
Isn’t that a bit of an issue?
For example, when handling URLs?
Don’t most Android packages begin with com. ?
[This comment has been deleted by an automated system]
@biscat @tanja yea
deleted by creator
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.