Ask HN: What are you working on (August 2024)?

Using PHP Slim Framework, MySQL, and vanilla Swift/Java. Prioritizing reliability and efficient sync between local storage and server. Currently finalizing API endpoints and feature matching the web app. Next up is adding a subscription model.

It's challenging as:

- Users want to use the app offline which means we need to sync

- We have to match our existing features on [2] in the first version and evolve the API and database to support reliable sync

- Users want to also track their cardio too e.g. Running Level [3] and Rowing Level [4] but that will have to come out in a future version

[1] https://strengthlevel.com/

[2] https://my.strengthlevel.com/

[3] https://runninglevel.com/

[4] https://rowinglevel.com/

https://github.com/WillAdams/gcodepreview

big things are reading:

_Abraham Lincoln and the Structure of Reason_ by David Hirsch and Dan Van Haften

and

_A Philosophy of Software Design_ by John Ousterhout

and getting the code to an actually useful state and then creating CNC joinery which isn't possible with other tools.

for example react is listed as high risk, but at the same time i would consider the risk to be very low in the sense that if it is relicensed then it will be forked immediately backed by a community that is strong enough to sustain such a fork.

i'd go as far as saying that for react relicensing would kill the project because the majority of users would go with the fork.

for other projects the risk is higher because they don't have a strong FOSS userbase that could sustain a fork, and because most current users would not care.