Taking inspiration from https://www.liftosaur.com/ , programmable routines would be valuable.
This could be used to create simple static routines/templates or complex routines (like automatically incrementing progressive overload).
Given this app runs in the browser, there's no need to write a custom DSL to describe routines - perhaps a simple JavaScript API would suffice where the custom script is run within a Worker thread (with read-only access to the end user's lift database) to ensure that it's safely sandboxed.
There will be challenges ensuring custom scripts don't send user data remotely. Perhaps I can lock this down with a locked down CSP.
I can use this engine to program some basic routines (like a simple chest day).
It would also be cool if it could schedule workouts, but that might be asking a bit much from the web
Taking inspiration from https://www.liftosaur.com/ , programmable routines would be valuable.
This could be used to create simple static routines/templates or complex routines (like automatically incrementing progressive overload).
Given this app runs in the browser, there's no need to write a custom DSL to describe routines - perhaps a simple JavaScript API would suffice where the custom script is run within a Worker thread (with read-only access to the end user's lift database) to ensure that it's safely sandboxed.
There will be challenges ensuring custom scripts don't send user data remotely. Perhaps I can lock this down with a locked down CSP.
I can use this engine to program some basic routines (like a simple chest day).
It would also be cool if it could schedule workouts, but that might be asking a bit much from the web