-
-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mobile Support? #652
Comments
If you are really desperate like me, you could do the following:
For reference, the path to my jrnl file within the Dropbox cache is
But is suspect it might be slightly different on each device, especially that random number within the path. |
This is a very good question. I have to admit that I hadn't considered the possibility that anyone was using jrnl on mobile. I don't know of any setups that currently work, but I suspect that you should be able to make work any terminal app (as long you find a reliable way to sync to your phone). If anyone knows of good setups, please post them here. We also have a milestone to rethink/rework the schema we use for jrnl, and have that time reserved to see how much work it would be to implement and maintain various third party integrations in jrnl (e.g. Day One, Red Notebook, etc). I think it would make sense to talk about mobile integrations at that time, too. If anyone has any ideas or recommendations, please post them in this thread. |
I was thinking about a dedicated mobile app that can read jrnl log files and permit the user to add/display entries. That said, the idea is to save your jrnl file in:
The app must be able to link with each service and locate the jrnl files (YNAB and other app follow the same approach using dropbox). |
I'm currently following @Jeinzi's suggestion and it's working "fine." The biggest offering that jrnl has over competitors is that it's file format is extremely easy to recreate and use. As things stand right now, you could totally use a normal mobile text editor to edit jrnl files but encryption/decryption and templates aren't options. Mobile app compatibility (maybe with StandardNotes?) is definitely the way to go, I just don't know how one would go about tackling the encryption / template issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
There's a lot of different ways to go about this! The solution could just involve adding various mobile platform-specific recipes in the documentation, or maybe something a bit more integrated. |
Closing this but keeping it in the ideas bucket. |
I store my journal file in Dropbox and use iOS shortcuts to append entries to it from the "Today view" screen. This is super handy for logging quick stuff like food journals. I also include automatic tagging based on the shortcut button that is pushed. My dream would be to have a DayOne style app which can read/edit jrnl files. I sometimes use ByWord to modify it from mobile but at over 4400 lines, it's pretty unwieldy. My only concern with an app that manages a flat file is the possibility of corruption but with Dropbox's 'snapshots', the risk is somewhat less. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
1 similar comment
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hey! I just discovered jrnl though a comment in this HN post. It looks super lightweight and like a great option for journaling, and the recent resurgence in maintenance is awesome. My only issue is that I can't seem to see a way to edit my encrypted journals via my android device. AFAICT, DayOne no longer works and I can't seem to find any other apps that are okay with the decrypting of the journal file.
Are there any known journaling apps or text editors that work well with jrnl? Thank you!
The text was updated successfully, but these errors were encountered: