Hello,

As per my earlier request, you haven't explained me context of these terms:

Models per app- As per tier 3, how these 30 models per app are mapped to 25 mobile apps. I need to know more context

Server less time per month- How is it computed and how should I know what time will I need for apps I want to build (as explained earlier), then only I can buy a suitable tier with this knowledge.

Subaccounts- For example in tier 3, you mentioned 25 subaccounts, that means I can give access to 25 customers (clients) through my main account. If yes, what all they can do with their access? I don't want to fix changes made later.

White labeling- Can I put my own company logo and link in each app, if yes where?

Thanks

It's hard to say what the learning curve is without knowing what you already know. So I will say that in general, Hypi is not a HTML/CSS builder so you cannot put in HTML/CSS and/or treat it like it is.

If you're familiar with Flutter then it is a minor learning curve since it is a visual Flutter IDE. An implication of this is putting screens together is based on composing smaller widgets into larger pieces of your UI to achieve your design.

1. This can be done, I suspect for videos you'd hit the data limits but otherwise doable

2. We don't have any built in crypto wallet features so this may not be a good fit right now. We're working on adding support for custom extensions where you or other 3rd parties will be able to make extensions available. This is scheduled for late summer so if it isn't urgently needed, it could be built with Hypi then

3. The math API we have should support the analytics features you may need for this, our charting widgets are not currently available publicly but we are working to make them available after some more testing, that'd allow you to do visual dashboards.

A model is how you store the data your app needs.
If you're building a pizza app then you may create a model called "Pizza" that has "name" and "size" as fields. This way you can create a list of pizzas for your app.

Within each app you have a limit on the number of these models you can create, so if you buy a tier that says the limit is 25 you can create Pizza and 24 other models.

I already explained serverless in one of your other questions where I explained about building a todo app. If that explanation is did not help then let me know what specifically isn't clear and I'll try to clarify.

A sub-account is an instance. If you create 1 pizza app and want to sell your app to multiple pizza stores then you will want their data to be separate but for the app to work the same way so you can create one instance (sub-account) for each of your customers.

Tier 2 and above allows you to white label...you can put your branding anywhere you want

Hello,

1. Actually I am confused with server less limits (each tier has different server less limits and what is your logic behind it), yes you gave example but what exactly is the meaning of server less here? Also sumolings are discussing offline apps, do they both mean same thing for you?

2. Do you have some kind of designer to visually build models, or am I suppose to just define fields to store data, am I suppose to understand relationships in advance and define keys for the table, which database type will store these tables. How is this model connected to UX (front end screens which buyer views)?

3. You didn't told me, how will I tackle inapp purchases and what about giving access to those who buy from Apple/android store?

4. Can I build PWA also with it and bypass stores all together?

5. Can I bring any third party extension to improve workflow or add functionality or that is not allowed? Do you plan to launch any extensions which will be part of this deal?

Thanks