this post was submitted on 18 Jul 2023
32 points (94.4% liked)
Apple
17525 readers
45 users here now
Welcome
to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!
Rules:
- No NSFW Content
- No Hate Speech or Personal Attacks
- No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread
Communities of Interest:
Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple
Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode
Community banner courtesy of u/Antsomnia.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Import/export is planned, but for now your data is synced up via iCloud (which I'm aware isn't technically a backup).
Out of curiosity, what kind of backup format(s) would you consider to be useful? CSV? JSON? Something else?
And thank you for your input regarding the price. All of the comments regarding pricing so far have been fair – everyone has their own limits as to what they're willing to spend on an app, and I appreciate the honest feedback.
Jeon and csv for me. Just so i can get my data out if needbe
See my above comment. I'm thinking JSON for sure, but we'll see about others.
I like the exports that Day One does if you've ever used that journaling app before (they do multiple kinds of exports). JSON, for if I need to write a script to import the data somewhere else. TXT for something nice and human readable. CSV for whoever wants to use this format lol. They also got a pdf printout just to make things look pretty. As for imports, I think they have import options for their competitor's export options, but I've only used this once and I don't remember the option I used.
But if it came down to just one, I'd say JSON is the most important for me. The other ones are just nice to have but not critical.
And np, I didn't want you thinking everyone thought it was too expensive.
Haha, thanks. I'm enjoying (and appreciating) the different perspectives being shared so far.
JSON would be the logical approach here, that way you've got an easy-to-follow structure of everything. (It also would be the easiest to implement.) I'll consider such a feature for the near-future.