• skates@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Is there an import/export backup feature of the data? One of the biggest hold backs for me when installing an app that’ll take me some time to set up is the fear I might have to restart if it gets abandoned.

    Also, $8 one time payment is totally fine in my opinion. It’s a one time payment and probably a useful app.

    • hmandlm@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      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.

      • skates@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        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.

        • hmandlm@lemmy.worldOP
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          1 year ago

          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.