Laufhelden is a sport tracking application for Sailfish OS. Laufhelden is german, meaning run heros.
I made this app mainly because Meerun is not maintained anymore. Features are well behind Meerun but there are some little advantages.
Meerun is closed source meaning if the developer won't maintain any longer, the app will die. Laufhelden is opensource so that problem should be avoided.
I am working out a few month with the app and really enjoy it, hope you also will!
To import workouts you can place GPX files in the directory ~/Laufhelden/
GPX files exported from Meerun will be recognized and hopefully workout type as well as a few other things will be imported.
To use the audio coach you can download the voice files here. Then you need to extract them and copy the folder voicefiles to your device under /home/nemo/Laufhelden/.
Current features are:
- recording workouts
- workout types: running, road bike, mountainbike, walking, inline skating, skiing
- view recorded tracks and show statistics
- save track as GPX file
- autosave every minute
- connecting to bluetooth heart rate device (supports Zephyr HxM BT and Polar Wearlink iWL, no BLE)
- show battery level of heart rate device
- use heart rate monitor from another application e.g. Amazfish
- voice coach witch cyclic updates and alarm thresholds
- default music player is paused and resumed when alarm threshold is triggered
- 4 display modes for record screen: AMOLED mode, LCD mode, silica mode, night mode
- automatic night mode
- upload workouts to sports-tracker.com
- upload workouts to strava
- pebble integration (needs Rockpool 1.4)
- lock page
- metric/imperial units
Please go here for more details of planned features or bugfixing.
Here is the TMO thread.
This application orginates from a fork of Rena by Simoma: https://github.com/Simoma/rena
Workout icons are from here: https://de.icons8.com/ They are under this license: https://creativecommons.org/licenses/by-nd/3.0/
Messagebox is from: Kimmo Lindholm, https://github.com/kimmoli/paint/blob/master/qml/components/Messagebox.qml
Credits go to:
This software is open source GPLv3. Sourcecode: https://github.com/jdrescher2006/Laufhelden
Please report bugs/issues to here:
https://github.com/jdrescher2006/Laufhelden/issues
If you wish you may donate for this project (it might boost my motivation a little bit ;-)): https://www.paypal.me/JensDrescher
Enjoy!!!
0.9.0-1, 12.09.2017
0.9.1-2, 12.09.2017
0.9.2-3, 22.09.2017
0.9.3-4, 26.09.2017
0.9.4-5, 16.10.2017
0.9.5-6, 31.10.2017
0.9.6-7, 16.11.2017
0.9.7-8, 19.12.2017
0.9.8-9, 05.01.2018
0.9.9-1, 15.01.2018
0.9.9-2, 16.01.2018
1.0.0-1, 06.02.2018
1.1.0-1, 04.05.2018
1.1.1-1, 13.07.2018
1.1.2-1, 14.09.2018
1.1.3-1, 24.12.2018
1.1.4-1, 27.10.2019
Comments
jdrescher
Fri, 2017/09/15 - 08:53
Permalink
The app has a autosave function. You can find the file in the ~/Laufhelden folder. If the file is there, and if you start a new workout, it should start from the old position. You could then regularely end the workout and save it to GPX file.
If this does not work, could you send the autosave file to me?
silta
Tue, 2017/09/12 - 21:08
Permalink
Thanks, nice app so far. Keep up the good work on it.
One request. Could you please display pace and average pace in minutes and seconds instead of decimal?
jdrescher
Tue, 2017/09/12 - 21:57
Permalink
Hi, thanks for your suggestion. I was thinking about this. Are you sure if this is standard in other apps? How is this done in Meerun?
silta
Wed, 2017/09/13 - 14:09
Permalink
In meerun it's done in minutes and seconds. I don't know what's standard in other apps since I only use meerun.
For me it's more intuitively to have minutes and seconds and it seems more consistent since total time of actual training and all trainings are displayed with seconds.
jdrescher
Thu, 2017/09/14 - 14:19
Permalink
OK, I will change this in the next release.
atlochowski
Tue, 2017/09/12 - 12:15
Permalink
I've added Polish localisation on GitHub.
jdrescher
Tue, 2017/09/12 - 14:00
Permalink
Thanks for that, you're damn fast!
I will put that in the next release. Give me a few days...
nodevel
Tue, 2017/09/12 - 12:17
Permalink
Thank you for the app/fork!
I just have to say it is quite raw yet and I don't mean missing features. The look of the app looks very non-native to Sailfish as it does not adhere to some best practices of SFOS UI development.
I apologize for this extensive critique - I really do appreciate the effort to replace MeeRun. The thing is, MeeRun was/is a great app for its variety of features, but it had two big faults:
So please do not copy all the features, with the faults above.
If you accept PRs, I would be happy to contribute some to the UI. Otherwise, I would recommend to read the Common Pitfalls in Sailfish Application Development article on Sailfish wiki.
jdrescher
Tue, 2017/09/12 - 14:11
Permalink
Hi @nodevel,
thanks for your feedback I really appreciate that. I'm afraid that I have to disagree on some of your points.
1. settings pages: that is a good point, I will rework this and have an overview page with a listview
2. Let's go button: starting the workout is the most important function of this page and I wish to have it in a prominent place. But I agree that a button is not the best solution. I will lilely use the Meerun solution for this.
3. Workout selection: this is a normal ComboBox, next to an image. The image helps identifying the workout type with just one look at it, no need to read the text. I did it that way because I wanted to bring the users focus to that. It is an important setting and if you overlook it, you have no chance to correct that later on.
4. Workout screen: I agree that an app should look as sailfish like as possible. But certainly not at all costs. I was very disappointed by the bad using of display space on every single sport tracker app I used before. I wanted to do that better. Also I liked the clear arrangement of elements in the original SPorts Tracker app on Symbian. This is also were the lines come from.
- there are lots of infos on that screen and the lines help sorting them out.
- padding was a little bit difficult, I will try to add that in the next version.
- colors are optimized for each specific display mode. The silica mode has system colors.
- buttons need background color for easy and fast identifying. I was not able to achieve that with default buttons.
- bottom pulley menu is in the middle of the screen only if the map is viewed. I took that from Rena and liked it so far.
- bottom pulley is a bit full. I will put some items in the top menu.
I might think about making the lines switchable and using the silica mode as default mode. That would make the record screen more sailfish like for the average user.
About the two big meerun faults:
- it never crashed a single time for me and I used it for years extensively. If my app is near as stable as meerun was, I will be very satisfied. Only problem is that it was not maintained for more than a year.
- I liked the UI of meerun very much and found it also very sailfish like. If you look in the feedback section for meerun and on Jolla together, you will notice that many other users agree with me. Some users even stated that of all SFOS apps, Meerun makes the best use of the UI possibilities. I mostly agree with that.
The biggest problem with the UI is certainly that people have different taste about the look&feel of an app. We should try to reach an agreement so that the UI fits most peoples taste.
As I invested much time in the app, I am not willing to throw everything over board, I hope you can understand my point here.
Instead of putting very much more work into the UI we should concentrate on missing features, like better statistic page with diagrams. Pebble integration would also be a killer feature for me, that would be so cool!
I have a suggestion for you. Let me do a rework of the points above in the next version of the app. After that we can talk again and I might accept pull requests about the UI.
I think for that kind of discussions we might need a maemo thread. Should I open one?
osetr
Tue, 2017/09/12 - 10:33
Permalink
Yes, the UI should be "Sailfishalised".
osetr
Tue, 2017/09/12 - 09:36
Permalink
Thanks a lot! Meerun's become really hard to use. Though Laufhelden currently is quet raw I'm happy to see it here!
jdrescher
Tue, 2017/09/12 - 09:48
Permalink
Hi, yeah there are a lot of missing features. Good thing is that I use the app nearly daily and thus am reminded of the lots of work to do. Maybe there are other developers who might join in...
Unfortunately I found a bug. I will upload a new version today.
osetr
Tue, 2017/09/12 - 10:31
Permalink
Maybe there are other developers who might join in...
I'll contribute with pleasure if I have time. Also I can participate in localisation.
jdrescher
Thu, 2017/09/14 - 15:25
Permalink
Thanks, that would be cool!
hias
Sun, 2017/11/05 - 17:34
Permalink
I also would like to contribute. How do you want to coordinate the development?
jdrescher
Mon, 2017/11/06 - 16:02
Permalink
Hi hias, what do you mean by coordinating the development?
Unfortunately I have not much experience with open source projects and multiple developers. On the other side, the code is on github and you can always do a pull request.
What would you like to contribute?
hias
Tue, 2017/11/07 - 00:20
Permalink
I'm contributing to KDE so I don't have experience with github.
Do I need access to your repo to create feature branches or do I need to fork your repo and then make pull requests?
By coordinating I just mean how to communicate on the features one is currently working on, so there is no double work. I didn't found a possibility on github to contact you.
I already played with the RecordPage and managed to make it look more like in Meerun, while still having the options to set the display mode. Furthermore I'm also quite interested in programming the graph.
jdrescher
Tue, 2017/11/07 - 09:02
Permalink
You need to fork and then make a pull request.
Currently I am working with ToDo.txt in my repo, the topmost section describes the points I am working on for the next release.
Maybe I should start a thread on TMO so that we can communicate about further development, is that OK for you?
That would be really cool if you can look into the graphs. I prepared that already on DiagramViewPage.qml. You can get there from DetaildViewPage, you just have to make the pull menu visible.
I took the diagrams from the app messwerk.
hias
Wed, 2017/11/08 - 00:11
Permalink
A thread on TMO would be great.
When I'm done with the RecordPage workover, I'd like to add lap support, because I need it for my use case. Right after that I would start with the graphs.
jdrescher
Wed, 2017/11/08 - 09:13
Permalink
I have created a thread on TMO: https://talk.maemo.org/showthread.php?t=100052
Pages