Contact access is a good example of permissions getting larger than the task. If you are recording that Maya borrowed the drill, the app needs a way to identify Maya. That does not automatically justify reading every contact stored on the phone.
Loan It uses Android's scoped contact picker for this job. You choose the contact through the system picker, and Loan It receives the selected contact for the loan record rather than getting general access to browse the address book.
Tap the borrower contact button
When you create or edit a loan, the borrower field can be filled manually or through the contact picker. Choosing the contact option opens Android's own contact-selection interface.
Select the person you want. Loan It resolves the chosen contact's name and uses that person in the loan record.
The permission matches the task
This is different from asking for broad contacts permission and then reading the whole database inside the app. The system picker mediates the choice. You decide which contact is handed over.
For a lending tracker, that narrower scope makes sense. The app needs the borrower attached to this record. It does not need a social graph.
You can still type a name
The contact picker is a convenience, not a requirement. If the borrower is not in your contacts, or if you simply prefer not to use the picker, enter the name directly.
That flexibility matters because a borrower record is not supposed to become a miniature CRM. The useful information is usually just enough to answer who has the item and to group that person's lending history.
Why keep a link to the chosen contact?
When you select a saved contact, Loan It can retain a device-specific reference to that chosen contact along with the borrower name. That helps preserve the association on the device without turning the app into a copy of the whole address book.
Device-specific contact links are not treated as portable data. Loan It's export and import system deliberately discards contact references that cannot be restored safely on another device, while preserving the borrower name in the portable loan record.
This is a useful model for privacy-sensitive app design
Permissions are often discussed as all-or-nothing choices: either an app gets contacts access or it does not. Modern Android can support a better pattern for some tasks: let the operating system expose the one thing the user deliberately selected.
The question is not whether contact information is useful. It plainly is. The question is how much access the task actually requires.
The tool used in this workflow
Loan It
Loan It tracks physical items you lend, including the borrower, borrowed and due dates, photos, return status, search, and lending history. Its borrower picker uses Android's scoped contact picker so you can select a person without granting broad address-book access.