I am currently developing some very basic apps for Android devices that utilise NFC stickers. A sticker is scanned and the device carries out a simple action. An example of this may be to call a certain number (held in the payload of the NFC sticker).
My original plan was to make an app for each action, as each of my customers will probably only have one NFC sticker. So, if someone wants to buy a sticker to call 999/911 (this is a fictitious example) then they only need the app that dials the number.
However, I will be pushing to sell other stickers, and I don’t want to flood somebody’s device with tiny apps when I can easily control it all from the one app. Let’s say I have 5 stickers that: toggle wi-fi, toggle bluetooth, dial 999, SMS home, call a taxi. Those would all require the following permissions:
- Bluetooth
- Bluetooth admin
- Wi-fi admin
- Make calls
- SMS
If I only bought the bluetooth sticker then I may become suspicious of why the app wants to make calls or send SMS messages.
My question is, what would be the correct approach here?
-
Lots of apps doing simple tasks and potentially annoy customers with multiple stickers (there will potentially be a lot of people with multiple stickers). Or,
-
One app that reads the payload of the NFC sticker and does the relevant action, but requests all of the needed permissions for all NFC stickers available (could be potentially dosens of unneeded permissions for an individual).
I am opting for one app, purely for ease of use. If app size becomes an issue it will be split into multiple apps.
To get around the permissions issue there will be a well-written description explaining the reasoning.