Connected systems

All project types · Shared launch

Extend useful applications into a connected workflow, preserving their records and letting each device serve its actual role.

Projects to build

• From a site visit to a finished report
• Your engineer at home, available from your pocket
• A research system that keeps up with your thinking
• A game night across different screens
• Capture outside and process on the computer
• A shared lending service with private working tools

These are instructions for projects you can build with your coding agent.

Let people use the service while you manage the work

Connect the shared lending library, native Tauri equipment desk, and a phone companion for physical handoffs. Build it extremely well. Members should be able to arrange a loan while the organizer prepares, checks out, and maintains the actual equipment. Follow the shared launch.

Begin with the collection, people, and working applications already present. Preserve item identities, existing loans, reservations, and maintenance history. Build any missing component around the same lending arrangement.

Give members useful access

Keep the hosted website available through ordinary browser access on members' own devices. Let them see the information needed to choose an item, request or reserve it under the group's rules, and understand collection and return arrangements.

Keep each owner's lending decisions intact. A request awaiting agreement, an accepted reservation, and an item physically in someone's possession should remain distinguishable across the system.

Show changes that affect a member's arrangement, including a delayed return or equipment becoming unavailable. Make the organizer's resolution visible to the people involved.

Let the desk manage the actual collection

Give the organizer a useful working view of requests, upcoming handoffs, outstanding returns, and preparation or maintenance. Retain the equipment desk's detailed item and kit records, condition photographs, history, and exports.

Establish a clear authoritative home for shared loan and availability information. Let the website, desk, and phone use it through meaningful operations. Preserve private working information for the people who need it while exposing the useful member-facing facts.

The organizer should be able to prepare a kit for tomorrow's loan and see that the member still expects it. A reservation change made through the website should reach that preparation work. When the desk takes an item out of service, its shared availability should reflect the decision.

Record what changes hands

Build a native phone experience for the organizer's actual device. Make it convenient to identify an item or kit, open the relevant loan, compare expected contents, and record collection or return while another person is waiting.

Use labels or scanning where they help with this collection. Let the organizer add a condition photograph and record a partial return. Record a tent's return while keeping any missing poles outstanding on the loan.

Keep phone entries saved through a lost connection and make pending updates clear. Bring them into agreement with current shared records when connection returns. Confirm new shared commitments against the authoritative availability, and give the organizer an understandable way to resolve a conflicting change.

Connect the public and private parts deliberately

Use the shared website's established hosting and suitable free services where they fit, explaining current limits and upkeep. Tailscale can connect the organizer's private devices for the work that needs it. Members continue using the hosted service independently of that private network.

Explain where important records live, which service must be running, and how to export and recover the collection. Preserve the useful desktop and phone work that can continue during a connection interruption.

Deliver a complete loan across the three interfaces: a member requests equipment, the organizer prepares it, the phone records the handoff, and a later return updates both the desk and member view. Include a missing accessory and its eventual resolution.

Teach how one shared service can cooperate with private tools. The website serves participation, the desk serves sustained management, and the phone serves the moment equipment changes hands.

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.

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, 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.

Build an equipment checkout and maintenance book

Build a native Tauri application for keeping track of equipment that people lend, borrow, and maintain. Build it extremely well for the actual collection and the people responsible for it. An explicit framework preference from the person takes precedence.

Follow the shared launch. Start by learning what equipment they manage, who uses it, and what currently makes lending it awkward. A school's microphones, a club's camping equipment, and a small workshop's tools each suggest a different working experience.

Know which item is which

Give each physical item a recognizable record with the details the person needs: a name, identifying information, useful photographs, its usual location, and relevant notes. Two items of the same model should remain individually identifiable throughout their history.

Find out whether things travel separately or in kits. A camera may go out with a lens, battery, charger, and case. Make it practical to record what actually left and check what came back. Use the collection's existing labels or reference numbers where they work well.

Help the person bring in an existing spreadsheet or list. They should be able to find equipment quickly by the names they use, see who has it, and understand what is available for an upcoming activity. If their work includes advance reservations, preserve the distinction between a future booking and possession now.

Make the handoff easy

At checkout, record the borrower, the equipment, the expected return, and any condition information worth preserving. Make it easy to include a photograph or a note such as “case latch is loose.” The app should be comfortable to use while another person is waiting for the equipment.

On return, bring the outgoing details back for comparison. Let the person record what was returned, what is still outstanding, and anything that needs attention. A kit can come back with a missing charger; the rest of the return should still be recorded accurately.

Show overdue items and upcoming commitments in a way that supports the person's actual follow-up routine. Give them the contact information and context needed to ask for something back. Decide with them whether reminders are prepared in the app or sent through a connection they want to add.

Keep the history useful

Returning an item and making it available again can be separate events. Equipment awaiting inspection or repair needs a clear status. Keep maintenance notes, repair work, and the eventual return to service with the item.

Preserve the sequence of loans and condition observations. Someone asking when a problem was first recorded should be able to inspect the relevant entry and photograph.

Let the person correct an entry, identify a misplaced item, or retire something from the active collection while retaining its history. Ordinary saved records and exports should remain accessible under the ownership and recovery arrangements in the shared launch.

Try a complete loan

Deliver an installed application with a representative part of the collection entered. Work through lending a kit, recording a partial return, arranging a repair, and making the equipment available again. Check whether the person can answer “Who has it?”, “What is missing?”, and “Can we use it tomorrow?” from the app.

Use this experience to explain the difference between an item's identity, its current condition, and the events in its history. The person learns why overwriting a spreadsheet cell loses information they may want later.

A later phone companion can scan labels and take condition photographs at the handoff. A shared lending site can let the actual group request equipment. Preserve the same item identities and loan history as those capabilities are added; the desktop book is already the working record of the collection.