Allows a property manager to input and organize move-in and move-out checklists.
How we built this appWe built this app using a Google Form and the AppSheet add-on. 1. Page one of our form contains a few qualifying details, like whether the property manager will be filling out the move-in form or move-out form, the unit in question, and the corresponding tenant's name. 2. The next page contains the questions concerning the condition of the unit. Later, it can be assumed the landlord might want to see what the move-in conditions were when filling out the move-out conditions, so we included two versions of each question, formatted like this: "Area: Move-In" and then "Area: Move-Out". Each question is a multiple choice that will render as a dropdown menu in the app. 3. Then we used the AppSheet add-on to create an app from our form. 4. We wanted to make sure that when the user creates a NEW form in the app, the first question defaults to “Moving in”. The intended functionality is that once a tenant is ready to move out, the landlord would simply go back into the initial move-in data for that tenant and then add the move-out data. That way one tenant’s move-in/move-out data is kept all in one place. To do this, we went to the Advanced Editor>Data>Column Structure, and set [Moving in or moving out? :] to "Moving in” as the Initial Value. This string is telling the “Moving in or moving out?” column to default to “Moving in”. 5. Though we want the landlord to be able to see the move-in data when filling out the move-out data, we don’t want the move-out questions to be available until move-out. To achieve this, we set an identical Show_If condition over each move-out question as follows: [Moving in or moving out?]="Moving out” This string indicates the app should only show these questions when the user has answered “Moving out” on the first question. In order to do this, the landlord would simply go back into past data and mark the first question “Moving out”. The app then shows both move-in past data AND the unanswered move-out questions. 6. In order to uniquely identify the data, we created a computed key comprised of the Unit and Tenant columns— it can be assumed one unit will never have two of the same tenants. 7. We then created a Data view and placed it in the hamburger menu. We wanted to be able to group by unit, and then by tenant, as this is a simple way for a user to toggle through the app. When he clicks “Data”, a list of units appear, and when a unit is selected, then a list of tenants living/who have lived in that unit appear. The user can then click into the entry he needs to update and hit “Edit”. This allows him to then choose “Moving out”— when he hits “Next”, he’ll see a list of the move-in data and blank entries for the move-out data he can then fill out.