Monthly app visits

[G2zo]

Hello,
In the pricing, we can see ‘monthly app visits’.
With the idea of producing an application that will be loaded on the client’s phone AND calls via API to Xano, what is the point of counting the number of ‘monthly app visits’?
In other words, are there any calls to weweb in this case and if so, why?
Are we talking about a native app, or is it an overlay that requires loading HTML pages from weweb?
Thank you in advance.

[dorilama]

Workspaces, pricing, and client collaboration

Hi Diogo, actually this did change since the last post in this thread back in January. The current pricing refers to app visits, which is different to page views. How do we count app visits? If a user opens their browser to visit a WeWeb app, we count one visit for as long as they stay on the app. When they navigate to other pages of the app, we do not count additional visits. If the same user closes their browser and opens it again to visit the same WeWeb app again, we count another visit. …

[G2zo]

Hello,

Thanks you for you answer.
So, it is not related to server resources from weweb.
Is the application a native application? Will all the data coming from outside be from Xano (in my case if I want my backend to be on Xano’s side) or their will be weweb connexions as well (thinking about scalability) ?

[dorilama]

Scaling is good in weweb.
See also this:

App hosting & & WeWeb Servers & HIPAA

Hi, it depends of which plugin and options you’re using. If you’re toggling the “proxy through server” on a REST request it will be forwarded by our server for exemple. If you’re using WeWeb Auth it will also ping our servers. If you’re using Airtable we have a microservice to hide your API key so it use our servers. If you’re using OpenAI its also a microservice to hide your API key and secure prompt. Except a couple of exception, anything else is a direct connection between your frontend …

[Alexis]

Your front end will be connected directly to your Xano instance! As long as your data collections are configured using the dynamic mode, meaning request goes from users’s browser to your backend without WeWeb as a middleman.