Open DavidLandes opened 3 months ago
I really like this idea! I think it's a good one to start with, since we could both put it into use right away.
I'm just trying to picture what the UI might look like. What am I missing?
Would this sort of app need to have syncing features? Really it might just be easiest to store the data in a single file, like a Google Sheet or local XLSX file. That would also allow the user to easily access their maintenance records and do whatever processing they want with those.
Would this sort of app need to have syncing features? Really it might just be easiest to store the data in a single file, like a Google Sheet or local XLSX file. That would also allow the user to easily access their maintenance records and do whatever processing they want with those.
This may be a cool feature in the future.
@Pertempto Feel free to add ideas to the Equipment
& Maintenance Tasks
sections in the description! This will give me a better idea of what things are more useful to you!
I need to think of a better term than "Equipment". This doesn't really make sense with some of the options like "Dryer Vent" or "Gutters"
Feel free to add ideas to the Equipment & Maintenance Tasks sections in the description! This will give me a better idea of what things are more useful to you!
Will do!
I need to think of a better term than "Equipment". This doesn't really make sense with some of the options like "Dryer Vent" or "Gutters"
Yeah, I get what you mean. It does seem to be a pretty intuitive term, so I wouldn't scrap it until we for sure have something better.
Could there be some sort of hierarchy?
So "dryer vent" would be a piece of sub-equipment under the equipment of "dryer"
"gutters" would be a piece of sub-equipment under the equipment of "roof", which itself could be a sub-equipment of "house"
This sounds complicated, but I think really it could be very simple to implement. Just add an optional parentId
field in the equipment
table
Possible alternative terms for "equipment"
Possible alternative terms for "sub-equipment"
I'm thinking that each piece of "sub-equipment" would be a full "equipment" in it's own right, it could just be a very useful thing for keeping organized.
In your diagram, I'm thinking really your "equipment" and "part" models could be combined
I added a few more off-the-wall ideas to your description. I'll add more as I think of them.
Is the goal of this app to just provide history?
Reminders of future maintenance would make it MUCH more valuable to me.
Even if for the first iteration it was something super simple.
This one would be so valuable to me that I'd be very interested in helping out with implementing it. I think we should go ahead with creating a repo for it, I think it's a good one to start with.
That way we can have separate issues for different areas of discussion, instead of filling this stream up 😅
I would recommend calling this app "Home Maintenance"
It would lead to a consistent "Home ____" naming scheme across many of our apps
This one would be so valuable to me that I'd be very interested in helping out with implementing it. I think we should go ahead with creating a repo for it, I think it's a good one to start with.
That way we can have separate issues for different areas of discussion, instead of filling this stream up 😅
I'll push an initial commit sooner or later. For now we can create issues instead of adding comments!😄
Home Maintenance
Description
The objective of this app is to keep historical records of when maintenance tasks were completed on equipment. It also keeps records of parts purchased to complete the task. It also helps to manage future/upcoming tasks with reminders.
Features
Structure
Equipment
Maybe?
Maintenance Tasks