Creating private transaction is very CPU demanding, which becomes a problem especially on mobile devices. The timeout for creating transactions has recently been increased (e7c4dfe) but having to wait several minutes for creating a transaction is clearly suboptimal from a UX perspective, if we want users to use Alias as a cash replacement.
Also in general high CPU usage on mobile devices is a problem simply due to reducing battery life.
The heavy operation here seems to be indeed the cryptography part. One idea so far is "optimizing the usage of the openssl library." as mentioned by @teknex on Discord
Creating private transaction is very CPU demanding, which becomes a problem especially on mobile devices. The timeout for creating transactions has recently been increased (e7c4dfe) but having to wait several minutes for creating a transaction is clearly suboptimal from a UX perspective, if we want users to use Alias as a cash replacement.
Also in general high CPU usage on mobile devices is a problem simply due to reducing battery life.
The heavy operation here seems to be indeed the cryptography part. One idea so far is "optimizing the usage of the openssl library." as mentioned by @teknex on Discord