# Build a lending library for people you know

Build a shared web application where a group can offer items, arrange borrowing, and keep track of returns. Build it extremely well for the way these people actually lend things. Follow the [shared launch](../shared/launch.md).

Use an ordinary link on phones and computers, hosted independently of the builder's computer. Prefer suitable free cloud hosting and explain its current limits. The builder owns the service setup; members join the application through an access method appropriate to the group.

## Learn the lending arrangement

Find out what the group shares and who owns it. A club's common equipment and tools lent by individual neighbors have different arrangements. Learn how people decide whether an item is available, agree on a loan, and confirm a return.

Let members or the appropriate organizer list items with useful descriptions, photographs, availability, and any instructions needed to borrow or use them. Identify particular physical items when that matters, including accessories that travel with them.

If the person already uses the [desktop equipment book](../desktop/equipment-checkout-book.md), carry the relevant collection and history into this project. Preserve item identities and explain which information becomes available to members. If both interfaces remain in use, keep their current loan and availability information in agreement.

## Respect how each owner lends

Let a member request an item for the dates they need and see the current state of that request. Some owners want to approve each loan; others make equipment available for members to book and collect. Represent those arrangements directly and make the process clear for each item.

Keep a request, an agreed reservation, and an item actually collected distinguishable. A member should know whether the item is theirs to pick up, when it is expected back, and how to arrange the handoff.

Handle competing requests or bookings accurately. When availability changes, let the people involved see the effect on their arrangements. Give the owner a practical way to change availability or resolve a request according to the group's actual practice.

## Know where the item went

Record collection, return, and any useful condition information with the loan. Let the responsible people report a missing accessory or a problem that needs attention. An item awaiting repair should have a clear availability status.

Show members the information needed for their own loans and give owners a useful view of what is out, due back, or awaiting a decision. Keep personal contact and handoff details visible to the people who need them.

Make corrections and changed dates straightforward while preserving enough history to understand the loan. Use reminders where the group wants them, with clear control over the chosen communication method and the information it sends.

## Lend and return something

Deliver the hosted application with representative items and member access. Use separate member and owner sessions to request a loan, agree on it, record collection, and return the item. Include the group's ordinary way of handling a changed plan. Judge whether everyone can tell what they need to do next.

Explain where the shared records live, who can change them, and how the person can export or recover the collection. Apply the shared launch's ownership guidance and explain any maintenance required by the chosen hosting.

Use the experience to teach what changes when other people participate in a personal recordkeeping system. Members gain useful actions of their own while owners retain the decisions that belong to them.

Later projects can add phone-based checkout, identification labels, or a private management desk alongside the shared service. Preserve the same items and loans as those interfaces become available.