Topics created by terik

API requests are calculated based on the requests you send. For example, if you want do download an element of the TODO list, you’ll perform 1 API request. The backend will send you the response that, of course, will not be counted as it’s not a request. Also, considering your example, if a user performs 10 updates in 1 day, that’s = 10 API request. If 10 users do the same, that’s 100 API requests. Hope it helps.

Of course it can, just remove all Monaca’s default references, like splashscreen, icons etc :) Some users decide to include Monaca or Onsen UI logo in their “about us” or similar pages, but of course that is something up to them.

Monaca and Onsen are great fits. The key to remember, is anything you can do in a web page, you can do in a hybrid app. This greatly reduces the expected learning curve if you just treat it like a web app. Onsen is a UI framework that makes your app simple to develop and maintain a near native user UX. Monaca has a variety of tools to help you build the app or plugins to gain functionality. So, having said that, your app would utilize HTML and JS to connect to your remote server. You can use Node.JS or perhaps PHP to interact with your DB. Returning results is best handled via JSON.

@munsterlander Tks for the info therefore,I ll keep on investigating, i like many features I’ve seen so far. :) Ooops, my fault, forget to include the ref URL: such as : https://docs.monaca.io/en/manual/backend/control_operations/ This page :for creating/adding a user: …but since some added Json prop specifies her name and age, I didn’t get it how this would serve for an new end-user signing-up for the first time. I guess this very case is for an Admin to add an already known user details to the table.