✅ Advice on possible architecture
I want to work on an app that can be used by speedrunners and score hunters. Basically, it either tracks time, or score.
I would like to know if anyone has some advice on how the data should ideally be structured to allow for a very versatile use. I basically want to create the "backend" here. It can then be turned into a website, or a CLI or desktop app. Compatibility with ASP/EF is therefore a small priority (whatever that means).
My first thought is to implement some sorts of "Attempt" and "Segment" types. Unfortunately, these would have to be mutable (start attempt, end later; undo/redo segments).
I would like to know if anyone has some advice on how the data should ideally be structured to allow for a very versatile use. I basically want to create the "backend" here. It can then be turned into a website, or a CLI or desktop app. Compatibility with ASP/EF is therefore a small priority (whatever that means).
My first thought is to implement some sorts of "Attempt" and "Segment" types. Unfortunately, these would have to be mutable (start attempt, end later; undo/redo segments).
