From 28ebd22d6079e11150ce97677a5622ce1144241c Mon Sep 17 00:00:00 2001 From: alex Date: Sat, 30 Aug 2025 12:52:22 +0000 Subject: [PATCH] Update Home --- Home.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Home.md b/Home.md index 1ef70e4..7a2192d 100644 --- a/Home.md +++ b/Home.md @@ -8,7 +8,7 @@ Naturally, one's own lifespan is impossible to predict with any degree with cert 1. The app must be compatible with Android 14 and newer. -2. It must display a screen on any form factor smartphone running Android that will show, represented in circles, the full number of weeks of the user's lifespan. Each week of that number must be represented by a separate circle. For example, if the user specifies a date of death and a date of birth interval that would cover a total of 942 weeks, there need to be 942 circles shown on the screen of the phone. Circles that have already elapsed (i.e. the weeks from the past as of today) will be shown in red, whereas circles representing the weeks into the future will be shown in green. +2. It must display a screen on any form factor smartphone running Android that will show, represented in circles, the full number of weeks of the user's lifespan. Each week of that number must be represented by a separate circle. For example, if the user specifies a date of death and a date of birth interval that would cover a total of 942 weeks, there need to be 942 circles shown on the screen of the phone. Circles that have already elapsed (i.e. the weeks from the past as of today) will be shown in green, whereas circles representing the weeks into the future will be shown in grey. 3. Upon starting the app for the first time, the app must ask the user for three key details about themselves: their full name (which should be a Unicode encoded string of no more than 100 code points), their date of birth and their date of assumed death. All of the three details mentioned should be editable in the future @@ -20,7 +20,7 @@ Naturally, one's own lifespan is impossible to predict with any degree with cert 7. The app must correctly handle leap years. -8. Dates of death into the past compared to the current day should be possible. A new user whose date of birth and death are into the past should be allowed to be created and their lifespan should be handled correctly. In such cases, the circles on the screen should all be red, obviously. +8. Dates of death into the past compared to the current day should be possible. A new user whose date of birth and death are into the past should be allowed to be created and their lifespan should be handled correctly. In such cases, the circles on the screen should all be green, obviously. 9. It should not be possible for the user to specify a date of birth that's later than the date of death. To prevent such a thing, the date pickers for the dates of birth and death should be on the same screen, and the user should not be allowed to be able to press the "Save" button if the dates are in the incorrect chronological order. An informative error message should also appear onscreen.