01 — The product

What it does

An état des lieux is the French legal inspection of a rented home: room by room, the condition of every element, signed by landlord and tenant at move-in and again at move-out. The two are compared when the tenant leaves. Most are still done on paper.

The app does it on a phone, on site, offline:

1. Describe the property, landlord and tenants, or import them from our web apps.
2. Walk the rooms. Per element: a grade, a comment, photos.
3. Count keys, read meters, list furniture (furnished lets).
4. Review, then send for electronic signature. Signers get an email, sign on their own device, and the signed PDF comes back into the app.

At move-out, the app pre-fills every grade from the move-in and highlights what changed.

Who uses it

• Small private landlords: a few inspections a year, not technical, need guidance.
• Property managers and agencies: several a week, back to back. Need speed and no re-typing of data they already have.
• Tenants never touch the app. They get the DocuSign email and the signed PDF.

Context: standing in an empty flat, one hand, moving room to room, often without network. 20 to 90 minutes per inspection. Customers are French; English and German exist. Room and element names stay French in every language.

The family of products

Signature can start from the phone (one credit, the report is built on the server) or from Docucéo after review. Either way the phone then shows the inspection as locked and follows the signature status.

Rules that shape the screens

• Draft from the first field. Nothing is lost; a draft reopens where it stopped.
• Six grades, green to red: Neuf, Très bon, Bon, État d'usage, Mauvais, Très mauvais. Averages give a room grade and an overall grade.
• Functioning scale for equipment (smoke detector): Absent, Working, Not working, Not tested. Not a grade, not averaged.
• Move-out pre-fills move-in. The user changes what changed; the summary shows each change.
• Completed is not locked. It signals "done" and uploads. Reopening asks for confirmation.
• Locked after sending. Nothing changes on the phone once sent, paying or signed.
• Guest mode. Everything works without an account except the free PDF and sending for signature. The app says so before continuing as a guest.
• Imported data is read-only at its source. Edits stay on the phone, marked "modified locally".
• Remote-only inspections. Done on another device or in Docucéo: listed with a "Sur Docucéo" badge, opened on a reduced summary.
• Credits. One signature request costs one credit.
• The checklist is the client's. Rooms, elements, furniture come from a spreadsheet he maintains, French only.

Where it stands

Version 1.10.0, October 2026, with a group of testers on TestFlight and Play. The full flow works. The look is the framework default lightly themed with the Appliceo colours. Nothing has been designed yet.

02 — Glossary

The product is French first. Every screen label exists in French, English and German, but the domain vocabulary and most conversations with the client are French. This table is the bridge.

Room, element and furniture names (the checklists inside an inspection) come from the client's reference workbook and exist in French only, whatever the app language. You will see them in French in the German screenshots.

Domain

Ecosystem

Status words on the Home list

03 — Screen map

Two shells. Signed out: the login screens. Signed in or guest: the main app with a drawer menu. The intro slides sit on top of either on first launch.

flowchart TD
  Boot[App start] --> Gate{Session?}
  Gate -- none --> Login
  Gate -- valid, offline
or guest --> Home
  Intro[Intro slides
first launch] -.-> Login
  Intro -.-> Home

  subgraph Login screens
    Login --> Register
    Login --> Forgot[Forgot password]
    Login --> GuestSheet[Guest sheet]
    Register --> VerifyPending[Verify your email]
    GuestSheet -- continue anyway --> Home
  end

  subgraph Drawer
    DrawerMenu[Drawer menu] --> Settings
    DrawerMenu -- guest --> Login
  end

  subgraph Main app
    Home[Home list] --> NewSheet[+ sheet]
    NewSheet -- from a lease / property --> Picker[Picker]
    NewSheet -- from scratch --> Wizard
    Picker -- lease --> Wizard[New inspection
5 steps]
    Picker -- property --> UnitDetail[Property]
    Home -- draft --> Wizard
    Home -- in progress --> Editor
    Home -- completed, locked, remote --> Summary
    Home -- create check-out --> Editor
    Wizard -- landlord --> EntityForm[Landlord form]
    Wizard -- tenant --> PartyForm[Contact form]
    Wizard -- start --> Editor[Inspection editor]
    Editor --> Room[Room]
    Editor --> Tenants[Tenants]
    Editor --> AddRoom[Add room sheet]
    Editor --> Camera
    Room --> Camera
    Room -- validate --> Room
    Editor --> Summary
    Summary --> Send[Send for signature]
    Summary -- reopen --> Editor
    UnitDetail --> Wizard
  end

Screens

Shared overlays: the bottom action sheet, native confirm and info dialogs, the photo caption editor, bottom sheets (add room, rename, guest mode).

What does not exist

No tab bar, no signature pad (DocuSign does it), no purchase screen, no dark mode, no tablet or landscape layout.

04 — User flows

Screenshots are the German build; numbers refer to the screen pages in 05-screens/.

A. First launch to first inspection (guest)

1. Update notice only when an app update has to wipe local data (rare, we try to avoid it).
2. Intro, four slides: on-site inspections, linked to Docucéo and Appliceo, signed with DocuSign, "let's go". Skip link on the first three.
3. Login, with "Continue without an account" at the bottom. That opens the guest sheet which states the two limits (no export, no signature) and offers create / log in / continue.
4. Home, empty. One call to action: create an inspection. The "+" in the header opens the action sheet: from a lease, from a check-in, from a unit, from scratch. The two "from" options need an account: as a guest they land on the picker's sign-in wall.
5. Wizard, five steps. Address (the unit is named after it) → type (check-in / check-out, lot type, furnished) → rooms (size band pre-selects, one switch per room) → landlord (choose or create; an agency also names the owner) → tenants (add or create). "Next" stays dimmed until the step is valid; a red "Cancel" appears once a draft exists.
6. Editor. Header block (name, type, date, address, landlord, tenants, each with a pen), the room list with progress, then add room, keys, meters, furniture (furnished), comment, general photos. Sticky "Summary" button.
7. Room by room. Each element: a 2 × 3 grade grid, a comment, "add photo". Equipment uses the 2 × 2 functioning grid. Footer: room comment, all photos grouped by element, general photos, then "Validate and go to ".
8. Camera. Permission screen → live preview → review with caption → saved, the element shows "Add photo (1)".
9. Summary. Status and overall grade pills, per-room and per-element grades, comment, then the actions. As a guest the upload row says "sign in to send" and the free download is disabled with "Account required".
10. Mark as completed → confirmation → "saved" info. Home now shows the row as completed with a "Create check-out" button.

B. Check-out from a check-in

1. Home → "Create check-out" on a completed check-in. The exit is created with the same unit, landlord, tenants, rooms, keys and meters, and every element pre-filled with the entry grade.
2. The editor opens directly. Rooms show the entry progress copied.
3. In a room, each element shows "Check-in: " and the entry comment above the exit grid. Changing a grade marks it.
4. The summary shows entry → exit per element with "degraded" / "improved", and the link to the entry. Home shows the pair as one block.

C. Account, import and signature

1. Register (first name, last name, email, password with a 12-character rule) → verify pending (the link opens in the browser on Docucéo) → login.
2. Signed in. The drawer shows the email and "Log out"; Home gains the remote-only rows ("Sur Docucéo") and the cloud icons; Settings shows the credit balance.
3. Import. "+" → from a lease / from a unit → the remote picker lists Appliceo and Docucéo records with a search field and an origin badge. Picking a lease pre-fills the whole wizard.
4. Upload. Marking an inspection completed uploads it ("Upload to Docucéo: sent on …").
5. Send for signature. One block per signer with an editable email (format, test domain and mail-server checks), the credit balance, the cost line, the button. After sending, the inspection is locked and the summary shows the signer statuses.
6. Remote-only inspection. A banner explains the inspection is not on this phone; status, header, signers with their status, signed files, "View on Docucéo".

D. Photo-rich inspection (demo data)

A completed inspection with photos, an agency landlord with an owner, two tenants, custom keys.

E. Furnished let

The type step has a "Furnished" switch; the editor then carries a furniture inventory, grouped by room and category, with a present / absent and quantity per item.

05 — Screens

Screenshots first, then a few lines: what it is for, what the user does, states, rough edges.

06 — What exists today

No designed system yet: the framework's default components, the Appliceo teal, one font. This is the starting material, not a constraint.

Colours

Grades, shared with the PDF:

Functioning scale: #1a8e4a Working, #bc2427 Not working, Absent and Not tested in the neutral greys.

Light mode only. A dark palette exists in code but is switched off.

Type

Space Grotesk, five weights, bundled (identical on iOS and Android). Body 16 / 24, section titles 20 / 32, labels 16 medium, small text 14 and 12. The PDF has its own styles.

Spacing and shape

Scale 2, 4, 8, 12, 16, 24, 32, 48, 64. Side padding 16. Cards and inputs: 4 px radius, 1 px border. Buttons: 48 px tall, full width. Chips: pills, outlined, filled when selected.

Icons

Ionicons (outline style): back, close, plus, camera, flip camera, trash, pen, image, chevrons, menu, person, home, document, check, eye, logout, cloud done, cloud pending. Any Ionicons glyph can be added cheaply.

Components in use

Native pieces we do not restyle: alerts, the legal-form picker, camera permission, the share sheet, the keyboard.

Motion

Intro slides and bottom sheets animate. Rooms and elements reorder by long-press drag. Screen transitions are the platform defaults.

07 — Constraints, and what we need from you

Hard constraints

NOTE FROM JEROME: I re read this and removed corporate horrors, there may be some left so don't feel offended by terrible things claude can say

• Phone, portrait, iOS and Android from one code base. Native dialogs, pickers, keyboard and permission prompts look different per platform and stay native. Smallest targets: iPhone SE width (375) and small Android (360).

  J: this one is less a decision that a rationale thing to do making correxct pickers take time we can change later

• Offline first. Every screen except login, register, the pickers and the send screen must work with no network.

• Light mode only for now.

• Reference names are French in every language, up to about 30 characters ("Détecteur de fumée", "Assiettes creuses / assiettes à pâtes").

• Three UI languages. French runs 20 to 30 % longer than English. Check the longest at the smallest width.

• Six fixed grades with fixed colours shared with the PDF. Their presentation is yours; their number, order and colours are the client's.

• Signature is DocuSign, outside the app. The app collects and checks emails, then shows status.

  J: this is true but it will print a html too i'll include it asap

• Locked means locked. Sent, paying or signed inspections cannot change on the phone.

• Photos are the heavy part. Sixty per report is normal; thumbnails stay small.

Product constraints

• French first. Propose copy in English; we translate.
• A signed inspection is a legal document, frozen forever. "Modify" means duplicate.
• The checklist is the client's: rooms, elements, furniture, grades.
• Guest mode stays. A whole inspection without an account, asked for one only at export or signature.
• Login is shared with Docucéo; verification and reset links open in the browser today.

Practical

• Releases every one to two weeks to testers. Pure UI changes are cheap; new native features (permissions, icon, splash) cost a store build.
• One developer. Reusing the existing components (06) ships fast; a new pattern is fine when it serves several screens.

What we would like from you

1. An audit of the current screens, problems ranked.
2. A visual direction that sits next to Docucéo's identity (teal, the robot) without copying the web.
3. Key screens redesigned, in this order of value: Home, Room (the one used most, standing, one hand), Editor, Summary, the wizard, Login and guest entry.
4. A component sheet for the pieces in 06, both platforms where they differ.
5. Flows for the rough parts: first launch to first inspection, move-out comparison, send for signature and after, remote-only inspections.
6. Store assets later: icon, screenshots, feature graphic.

Figma is easiest for us. Name frames by the screen numbers used here (05 Home, 14 Room…).

J: what claude mean here is HE prefer figma, because it explain things to an ai in the format than say illustrator I, JEROME don't mind what you use, but it figma IS an option we will gladly take it

08 — Known issues and open questions

Known, accepted for now

• Verification and password-reset links open in the browser, on Docucéo; the user comes back to log in. In-app links are planned.
• The overall grade is a plain average and misleads with sparse grading. Planned: show it as a suggestion with a manual override.
• The checklist (rooms, elements, furniture) needs an app release to change.
• In-app purchase of credits exists in test builds only; production users buy in Docucéo.
• "ZIP export (development only)" on the summary is a developer tool.
• Property and lease lists exist under Home but their tabs are hidden.
• Home search and filters coexist; their interaction is not final.
• A report above a size limit cannot be signed; a photo-count warning is planned.

Noticed while taking these screenshots

• Confirmation dialogs show French buttons in the German app (Annuler / Confirmer).
• The update notice ("this update clears the inventories") shows on a fresh install.
• Auto-generated names title-case the street ("12 rue Des Lilas").
• The room screen shows a red trash icon on every element at all times; the editor shows it only in edit mode.
• Settings shows the credit section to guests, disabled.
• Login and register buttons are dark grey; every other primary action is teal.
• Two "edit" idioms: pens next to header fields, a text link for the room list.
• The furniture inventory nests three levels (room › category › item) with counters like 0/91; hard to scan.
• Move-out rooms pre-fill the move-in grades, so an unvisited room looks done.
• The keyboard covers the lower fields of long forms on Android.

Questions for you

1. Home: is the list the right home, or should the current inspection come first?
2. Room: the grade grid takes most of the screen per element; is a compact row with an expand better for 10 to 17 elements?
3. Move-out: how should "unchanged" versus "changed" read at a glance?
4. Guest mode: a sheet, disabled buttons with "Account required", a sign-in wall in the picker. Three patterns for one rule. Which wins?
5. Locked state: greying every control is honest but noisy. What should a sent or signed inspection look like?
6. Remote-only inspections: like the others in the list, or clearly "elsewhere"?
7. Dialogs: keep native alerts, or design in-app ones?
8. Dark mode: worth designing tokens for, or leave off?

Out of scope

The report PDF (shared with the web app), the Docucéo and Appliceo web screens (a separate hand-off will cover Docucéo's part of the inspection flow), store listing copy.

09 — Brand and assets

There is no written brand guideline. The brand is a colour palette, two logos and a mascot.

Files in assets/brand/

Brand colours: teal #3edfcf, #25c2b2, #2a9995, #007267; action orange #ffa107, #ef7600. Docucéo (the web app) uses the same teal with a cooler, oklch-based ramp and the Manrope font; this app uses Space Grotesk. Aligning the two is an open question for you.

Store material

assets/store/: the current Play Store feature graphic and two framed screenshots (French). The store listing text lives in store/listing/ in the repository (French and English). The screenshot frames are generated from an HTML template in store/src/; the source captures are raw phone screenshots like the ones in this folder.

Report

assets/report/sample-report.pdf is a real inspection report produced by the app (with the client's anonymised data), and report-page-1..3.png the first pages rendered. The report is the deliverable the customer keeps and signs; its layout is shared with the web app and out of scope for this hand-off, but it shows what the data collected on the phone turns into.

Illustrations

The intro slides use four illustrations drawn in code, animated. They are placeholders: a phone with a checklist, the robot, a signed page, a start screen. Replacing them with your artwork means SVG or Lottie.

10 — TODO

What remains to be added to this document before it is complete. Each item becomes a section of its own in a later version; the version history in 11 says when.

• Docucéo flows. The web half of the journey: how an inspection report is reviewed, paid and signed from Docucéo, how signed documents are downloaded there, and what the user sees in the phone meanwhile. Screenshots of the web app, same test account.
• Reports. The end product: the PDF and the HTML version of a report, page by page. Full version with photos, light version without, the move-out comparison. What is fixed by law and what can change.

11 — Document history

This document has its own version, independent of the app version. The newest entry is first.