Comment by throwaway77385

The most substantial one is a local business directory. It's exactly the right level of medium complexity where Pocketbase shines. It's all the standard stuff:

- User signups and auth

- Stripe subscriptions using different subscription levels

- Business listings with image galleries, editable images

- Map with markers for business locations, tags, filterable business categories & tags

I'd say that the way Pocketbase handles collections, you probably don't want data that is too nested (even though there's a JSON type field, which then allows much deeper nesting).

If you're coming from Firebase, you might be used to infinitely nestable collections, but that's not how it works in Pocketbase. So you could either have a ton of collections or use nested data.

But, if for example, you had multiple clients which then need to hold a bunch of nested data, you couldn't have a 'clients' collections which then holds a bunch of collections within it. It's just one level of 'collections' within which each item then has fields.

This works well at medium complexity, but could get complicated if you had, say, a CMS where you'd want a few levels of nesting.