Say hello to your personal video game butler! GameButler supercharges your gaming habits and helps you spend more time playing the games you love.
GameButler is the best way to track what you’re playing, what you’ve played, and what you want to play. Track upcoming games, add games to your lists,…
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.
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.
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.