This idea requires much more flushing out and can easily balloon into complexity beyond its immediate needs or usefulness. This can quickly make it too complicated and therefore detrimental to the user. Furthermore, it is generally best practice to keep things, especially of a systemically recurring nature, on the simpler side. In lieu of this, it may be useful to impose limits (to start out of a lack of engineering resources and maybe later intentionally) on just how complicated these can be. Start very simply (days of week, every other week, days of month) and see what people want.
Time relative to an absolute time, used in formulas to create absolute times. The formulation of this exists in the following combination
List daysOfWeek = [Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday]
List months = …
List xthDayOfMonth = [first, second, third, fourth, fifth, sixth]
List dayNumbers = [1, 2, …, 365]
int frequency;
int everyTimeframe;
List timeframe = [second, minute, hour, day, week, month, year]
examples
The second and fourth (xthDayOfMonth) Monday and Tuesday (daysOfWeek) of every 2 months
where: a physical location
absolute location
relative location
implementation
location tracking
Provide functionality similar to that of the the Gyroscope app, as seen to the right. Tracks location at all times then let's people create locations tied to coordinates (try to find existing library)
Priorities
Chronological location log with map. Distinguish moving vs not. People can create “where’s” (PRIVATE OR PUBLIC)
Allow people to create sublocations (desk within room within house)
Automatically tie
Allow people to adjust ra
Modes of transport
Implementation
Use geolocator Flutter package
What accuracy to set to?
how
How is the rules, underpinnings, and principles of the universe.
what
who
why
future
features
easy data entry: press and hold to open menu w/ options of voice/text, photo/video,