It's planned via https://github.com/LemmyNet/lemmy/issues/2631 once lemmy supports.

Without that, there's two ways to do this with major drawbacks:

• Background tasks (android supported-ish with iOS support only with app open): Apps like Thunder are doing partial implementations by essentially polling the lemmy server in the background. I don't think this is very neighborly because it puts a strain on Lemmy instances with the polling per account every 15 mins. It also consumes more battery. And is not consistent depending on Android device manufacturer.
• Storing JWTs on a server: Some apps do this, but this is a nonstarter for me due to security/liability reasons

So IDK. Right now I feel pressure to do this because other apps support but the ways they are accomplishing this are pretty questionable.

Last time this was brought up, I believe the Voyager dev (sorry can’t remember spelling of his account, I think aeharding@lemmy.world ?) mentioned this is dependent on a proper resolution of push notification support from Lemmy itself, and linked to a Lemmy issue on GitHub. Very unfortunately, Lemmy devs doing what they do best — finding creative ways to alienate their user base by choosing a platform that only works on Android, requiring a third party app to background continuously, shoots down open web standards, and mislead iOS users to go create tickets in their chosen upstream project for fictitious “battery concern” when brought up that iOS paradigm does not allow long running background apps.

I’m not holding my breath for this :(