Setting Up a Mobile Project with Capacitor

[HeikoK]

@Mr.Rubi

For some reason, you took my words out of context,

I apologize, this was not my intention!

@Mr.Rubi

a request is made to a database, the total processing time of which takes 20-30 seconds, and the received data takes 10-20 megabytes

To be honest, this is a use case I never had in my life, except data reporting on platforms, but not for the end user. Both numbers, 20-30 seconds of processing time on the server and 10-20 MB of data transfered to a client. This sounds more like a edge case to me (except some heavy image processing?)
Would you mind giving a real world example where this is required?

@Mr.Rubi

If your application uses complex queries with a large amount of data or server computing, without using service workers, applications based on Capacitor/Cardova will greatly lose performance to native and Flutter-based applications, since they will use additional threads (kotlin/swift) or isolates (flutter) to process complex queries./calculations. This frees up the main thread, which is responsible for rendering the interface.

Why does the client suffer in terms of performance when the server is taking longer to respond? The request is async, the client is just waiting for the data stream while the rest of the UI is still working (regular Promise)? The main thread is not blocked here?

[NewMedia]

Perhaps duplicate George’s comprehensive Tutorial here as a separate post in the Tutorials category to give it top billing and easier to find in coming days?