Should I Use MobQL?

(TL;DR if you're just making a small website, probably not)

MobQL is not intended for use by everyone. It's built with a few utilities in mind that don't apply to all situations.

Data Heavy Applications

MobQL was first built with data heavy applications in mind. When dealing with lots of types of data or objects with lots of properties, queries can become more time-consuming to write.

Every time you add an extra feature you need to add another query or modify an existing one. With MobQL, all the data fetching is handled automatically, leaving you more time to tinker, even at runtime, with no need to modify your queries manually.

Lazy-loading

This also allows data to only be fetched when it's actually needed. For instance if you have a toggle to hide certain data, like tags on a list of items, users who have it hidden wont even fetch the data to begin with, saving them on bandwidth, and saving your servers query time to the database. The moment they switch it back on, the tags will be fetched right away.

Query Merging

Another advantage comes when a certain object might be shown multiple times on the same page with different properties being shown in each place. In a normal GQL client, requests might get queued for both areas at the same time, which can lead to fetching the same properties multiple times, which can get expensive on large sets of properties or properties that take more server time to fetch.