Start a new topic

How to see users and their number and other numbers


today I've logged in and noticed that now it's a new web console.

I've played a little bit with it and feel disappointed.

Firstly I can't see any pagination for users. Okay I can scroll but it's less convenient because it's slower. But what I definitely can't have now is a number of users.

The same with collections. I just want to know how many records I have for this specific collections. How?


Hi Kath,

As you noticed, we have just rolled out a new version of the console. While it's almost feature-complete with the previous console, there are still a few things we're working on. We are getting those into the new console as soon as possible, but if you need to access these features in the meantime you can still access the old console at
Kath -

First up, thanks for the feedback. It's extremely helpful for us as we iterate on the UI and continually try to improve things. We want to deliver the best developer experience possible, and sometimes that means a few bumps along the way as we make these improvements.´╗┐

Great catch with the collection count. We'll work on including that count, but in the meanwhile to get the count of your collection you can GET to `/appdata/YOUR_APP_KEY/COLLECTION_NAME/_count´╗┐` in the API console, or access the old console for a limited time at

As for the pagination, one of the core reasons we implemented the infinite scroll approach was to be faster than paginating, so yours is definitely not the result we are aiming for. If you don't mind me asking, how many fields/columns of data do you have in your users collection? And kind of hardware are you running on?

One current issue with the new databrowser interface is performance with lots of columns. We are working to improve this, but in the meantime, if things are running slow you can try hiding more columns to improve the rendering speed.

Thanks again for your patience, hope this helped!

thanks for answers.

Dave, I really don't understand how the scrolling could be faster than pagination. Even if I have not so much records (up to 100) it's slower because page has only 20 or 40. Another advantage of the pagination is you can see approximately how many records you have. For example if you see 3 pages today, and 4 pages tomorrow it's obvious that the difference is approx page. And you can see it without doing annoying _count request in the API console but just updating the page. Probably I'm wrong and nobody needs it but before it was and not now, it's a pity.

As for you question I have up to 100 records (somebody definitely has 1000 times more) and amount of fields is about 20. I'm running it on a pretty fast 2-core computer in Chrome. It's not slow but it's slower than before.


Login or Signup to post a comment