Vision for this app

[pprotas]

Hello! After spending a lot of time searching for the perfect workout tracker (even attempting & failing to learn Swift to do it myself...) I've come across this app. Surprisingly it's open source, and implements many of the functions I need!

Some functionality seems to be missing, though. For example, being able to complete/modify your set from the Apple Watch. The app 'Strong' has a very good implementation of this functionality, and I think this app could also benefit from this feature. It allows the user to not even take the phone out of their pocket during the workout.

Is this app still under active development? Is this a planned feature for the app? Is there even a roadmap? I want to help to make this app better, and will contribute, if this is something that would be appreciated for this project. I'll have to get better at SwiftUI first, though :D

[karimknaebel]

Hi, due to time constraints Iron is not really in active development anymore. I use it myself multiple times a week during my gym sessions, so I will still make sure that it keeps working and bugs are fixed.

Finishing a set from the watch is indeed useful, but I haven't found the time to design/implement it yet. This and integration with the new "live activities" in iOS 16 would be great though.

[fulldecent]

Hi @kabouzeid can you please say if you would still be able to do this minimal thing as maintainer for the project:

1. Add a "please-proceed" tag to issues that, if fixed, may be included in the product
2. Review and merge PRs if they are ready and implement a "please-proceed" issue
3. Sign, release and distribute app to App Store after merging

Thank you. And if so, perhaps it will be good to say this in the README.

[SmartBoy84]

Following on from the previous comment, if time constraints are an issue for you then you could also look into employing github actions to automate pretty much the entire process.

All you would need to do is review the PRs and approve them.

@kabouzeid @fulldecent

[karimknaebel]

Properly reviewing PRs and weighing the cost/benefit of how a new feature is implemented is the time intensive part of the process.

[fulldecent]

A way to make that less time intensive is:

• Add a "please-proceed" tag to issues that, if fixed, may be included in the product. This means there is already a decent chance a feature could pass the cost/benefit threshold.

and/or

• Add a PROJECT SCOPE section to README.md explaining the kinds of PRs that could possibly be merged, what definitely will not be merged, and how to make your review process as easy as possible. (Attaching screenshots of functionality, attaching screenshots using specific devices or test configuratitons, code style.)