Daylio has been requested before (and I just saw it has 4 upvote, so I am guessing its pretty popular ?) https://github.com/journiv/journiv-app/issues/58

Daylio kind of mood tracking i.e. extensive with custom mood and with activities will come soon.

Import from Daylio is possible although I am not sure how much the demand is. The github repo has lot of import from request from different apps and import does take a lot of time to build as most apps have obscure formats and nuances to deal with or on purpose don’t support simple portable formats to lock down user data. For example see the circus one has to go through to get meaning from Daylio export: https://www.joelotter.com/posts/2022/01/daylio/

Can you clarify the export issue you are seeing or please report it on github? The export/import has been working well. I am guessing you might have tried it out with quickstart docker compose or Synology NAS guide from mariaus hosting which does not have complete docker compose i.e. it is missing celery-workers container which are needed to create import/export jobs and run them async. Couple of users tripped on this so I will be improving the error message to specifically say they need to run complete stack right not the error message is very cryptic low level detail which is hard for anyone to understand what went wrong.

Hello, Sorry for the late reply. I do not use lemmy that often and only saw this now when I came here to post about new release. You’re right to call that out. I made an oversimplified claim. Let me clarify, XML vs JSON performance is nuanced:

1. Parsing speed: JSON is generally faster to parse than XML because:

• Simpler syntax (no opening/closing tags, no attributes vs elements decisions)
• Less data structure overhead
• More direct mapping to native data structures in most languages

2. Payload size: XML is typically more verbose due to:

• Opening and closing tags
• Namespace declarations
• Attribute syntax
• This means larger network transfers

However:

• Well-optimized XML parsers can be very fast
• The difference matters more for high-volume APIs than occasional journal syncs
• For large text content (like journal entries), the actual content dwarfs the format overhead