You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
First of all i'm really happy with zap developing.
I find out slowdown at app opening since v41 i mean not really a problem just few seconds (maybe because i have a mobile wallet installed that i don't see?)
About movement page, i find it confusing.
I know there are issue open for better Visual design that i think it's most of the problem, an easy way to visual recognize the different payment
But also the filters system is not clear to me.
For example there is on chain/lighting but if you deactivate lightning i expect to not see payment received but with created invoice On it shows it.
I will think something about it in the next days i know is not an easy task and it's not usuful just say that for me is confusing.
Anyway what really is important to me is security and reliability. Thats what i prefer as priority.
The text was updated successfully, but these errors were encountered:
First of all i'm really happy with zap developing.
I find out slowdown at app opening since v41 i mean not really a problem just few seconds (maybe because i have a mobile wallet installed that i don't see?)
About movement page, i find it confusing.
I know there are issue open for better Visual design that i think it's most of the problem, an easy way to visual recognize the different payment
But also the filters system is not clear to me.
For example there is on chain/lighting but if you deactivate lightning i expect to not see payment received but with created invoice On it shows it.
I will think something about it in the next days i know is not an easy task and it's not usuful just say that for me is confusing.
Anyway what really is important to me is security and reliability. Thats what i prefer as priority.
The text was updated successfully, but these errors were encountered: