-
Notifications
You must be signed in to change notification settings - Fork 129
Low maintenance mode #1110
Comments
I can understand that..... Your audience is very grateful people - not Google |
I'm grateful for this app - I use it everyday but I understand how annoying this has to be. Thank you for your work! |
Just want to thank u for this app. It is still my favourite app for todo.txt |
Indeed. The best app out there. |
If it helps your motivation, there is a great Windows/Linux/Mac desktop todo.txt app called sleek. The developer is responsive like yourself and his effort made todo.txt significantly more usable for regular users and todo.txt enthusiasts alike. I think the efforts of you both are appreciated by many, myself included. I hope you get motivation from the fact that you improved our lives, Google notwithstanding! 😀 Edit: link to sleek. |
I've been using ST Dropbox version for a few years. It is truly a one of a kind app, is easy to use, and can be used to manage simple as well as complex projects. It's ironic Google has been an obstacle as it's THE best app of it's kind. How can it be so under-rated? |
I don't mind F-Droid. I actually prefer it to gplay whenever an app is on both. |
I would really like to have a good way to separate the storage backends from the app itself, this would make maintenance much easier. The Android Storage Framework is a crappy deadend. |
I am super happy with Syncthing handling the storage and using the cloudless version.. but it doesn't really solve your problem 😅 just a very happy user! |
Similarly, I used cloudless + nextcloud handling syncing for a long time, and was generally happier with it than I was with the short time I used the ST Nextcloud flavor— it handled conflicts more gracefully (although they were more common) and didn't run into issues during first setup when the files on Nextcloud were not what ST expected to find. The problem is that Google keeps making it harder to get disk access which enabled this. But since we are no longer on the Play Store anyway, perhaps it does not matter. |
I remember seeing some way to send intents between apps, but limit which other apps can see them (i.e. to only your own apps). That would enable storage providers to be separate apps. Unfortunately, I'm having a hard time remembering what it was called & finding it :/ (We should also probably take this discussion to a dedicated issue) |
I am currently not using Android anymore, so I don't expect I will be spending a lot of time on Simpletask anymore. |
Not going to lie that's a bit of a disapointment but it is what it is. Thanks a bunch for all your work on Simplatesk! Persoanlly I just ended a two months trial trying to make Todoist work for me but in the end I returned to todo.txt. Will continue to use Simpletask for the time, after all for my needs it's feature complete. |
This is bad news, I'm pretty certain there's nothing close to Simpletask's functionality out there, I love it. Fingers crossed it won't break for a while at least. Thanks for such an outstanding app. |
Many thanks for SimpleTask! Please could you pin this issue (lol, already pinned) and edit the original description to add a link to your recent comment? |
I'm so sorry you had so much troubles with Google SAF and Google Play constant rejections, the lack of support and proper documentation is properly infuriating. You are not the only major Android opensource dev to be driven away by these antics. I worked on 2 other task managers before that experienced the same issue with SAF and succesfully implemented a Google Play friendly solution that is somewhat future proof because based on a 3rd party library called SimpleStorage. I know this is unlikely to make you come back, but when I'll have some time (so no ETA) I'll try to implement this solution as a PR, if you could just have a look it would be great! |
The suspending of the applications by Google #1102 and the continuously fixing breakage by Android API changes have reduced my Simpletask motivation to a very low level.
Please don't expect a quick response on new issues or PRs.
The text was updated successfully, but these errors were encountered: