[{"data":1,"prerenderedAt":34},["ShallowReactive",2],{"arch-deep-/architecture/resident-app":3},{"id":4,"title":5,"body":6,"category":23,"deepPage":24,"description":25,"extension":26,"layer":27,"meta":28,"navigation":29,"path":24,"relatedFlows":30,"replaces":30,"seo":31,"stem":32,"__hash__":33},"architecture/architecture/resident-app.md","The Resident App",{"type":7,"value":8,"toc":19},"minimark",[9,13,16],[10,11,12],"p",{},"The resident app is the primary surface through which a resident encounters the operating layer. Its design follows a single principle: residents should not experience the system, they should experience the building. Every workflow the building offers — entering a space, booking an amenity, reporting an issue, receiving a delivery, paying rent — is one place, with consistent rules, reliable confirmations, and a single source of truth.",[10,14,15],{},"The app is offered as a white-labeled native experience and as a progressive web surface for residents who do not install apps. Brand customization spans typography, color, copy, and the building's identity — but the structural elements of the experience, the workflows, and the response times are governed by the behavioral standard. The app cannot be themed in a way that violates the specification.",[10,17,18],{},"Offline behavior matters. The app maintains a cached representation of the resident's permissions, recent bookings, and active issues. During cloud connectivity loss, access decisions and amenity check-ins continue through the edge gateway; the app shows a clear offline indicator and reconciles state when the link returns. Residents should never see a blank screen because a cloud service is degraded.",{"title":20,"searchDepth":21,"depth":21,"links":22},"",2,[],"flow","/architecture/resident-app","The resident-facing surface — features, design approach, and brand customization.","md","3",{},true,null,{"title":5,"description":25},"architecture/resident-app","PRe69T940LAG_OajAVqRuOW_U6Dg4cSupB_EYFz3UWs",1779718756836]