Yana is much more fluid on my phone. Amethyst kinda lags a bit while checking my timeline.
Plus Yana loads all pics etc always while in Amethyst I found some moments that it does not.
Othe thing I found is that while on background Yana pings my relays every 30 secs or so, so not very much like this.
Is Yana still under development?
Absolutely.
Next release in few days.
Main new features:
- gossip (outbox/inbox) model
- nip51 relay sets for blocked/search
- local DB cache for feed/profile/notifications
- login as....
Follow nostr:npub1gp4xzpmluelsakjtayc4wtzj97fhj5kakqjvsannu00xkdlf4x8s0xdqyq to be up-to-date
Well, it is designed to run faster in older phones. So, I think nostr:nprofile1qqsrq7p2sv3m0jvtzuk952hhyp4ms2puv4d7dhwwzyfnvydq8403zacpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0jt3qyc achieved his goals :)
I spent few days trying to make amethyst faster on my s20 phone (which being 2 years I don't consider old), but finally gave up and started in flutter.
S20 was released before the pandemic, on Feb 2020. So, its just 3 months away from being 4 years old. It's old. Most importantly, this CPU was released before the UI Framework we use (Jetpack Compose) and doesn't have any of optimization for it. I am not sure there is much we can do.
Yeah I'm bit in denial about it being an old phone.
But the fact is that flutter code can make it quite usable.
Can you confirm if primal native android code is not using also jet pack composer? Because they're also quite fast UI on my phone. Maybe it's not a jet pack compose issue but something related to how amethyst uses live data or similar, I don't remember exactly what was the problem. It's on some github task comments...
It's about the number of components/clickable components in the screen/each note. The more you add the worst it gets. We might have added too many. :(
I did try to comment most of the feed components on amethyst's code and leave just a simple list and it still was not fluid enough. That's why I suspect something related with how data listener/consumer model is handled.
On my S19, I have to remove the rich text of posts + relay icons + turn most of the SVG icons into bitmaps to run smoothly. In the notification, I have to remove the clickable element of each of the author pictures. :(
Of course, if we can minimize the processing of new events, that helps as well.
I am currently refactoring the base caching system and the new one should help, but it is a lot of work.
It will check for notifications every 60s if you have the setting pull background service turned on.
This is to avoid needing google fcm push dependency and still get notifications.
Turn it off if you prefer.
I will add a setting for choosing how often.
This setting is off. I turned it off to test it but it keeps pinging. Maybe adding ntfy as an option ?
Though I didn't see notifications from Amethyst using ntfy..hmmm will test more.
U using 0.11 version? If so and it is off then it's only until android system doesn't kill it. Next version has a complete rewrite of relay socket connectivity and will stop any data fetching on background with pull setting off.
