# Firebase retrieval speed test

**URL:** <https://community.thunkable.com/t/firebase-retrieval-speed-test/1296904>\
**Category:** Questions about Thunkable X\
**Tags:** firebase\
**Created:** [May 21, 2021, 1:34am UTC](https://community.thunkable.com/t/firebase-retrieval-speed-test/1296904 "2021-05-21T01:34:27Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [May 21, 2021, 3:42am UTC](https://community.thunkable.com/t/firebase-retrieval-speed-test/1296904/6 "2021-05-21T03:42:58Z")

</div>

I’ll check that. Also, your idea to grab the whole data set and parse it using object blocks is something I was working on.

But I got sidetracked trying to get the new node[index].property text strings to work instead of the old nested property of object blocks. The ones here:

> [@API JSON Tutorial (Video)](https://community.thunkable.com/t/api-json-tutorial-video/1140575/15):
>
> Interesting… I just got an email from Thunkable about a new feature available within text boxes, related to APIs and JSON parsing: [https://docs.thunkable.com/objects#nested-values-and-values-from-arrays](https://docs.thunkable.com/objects#nested-values-and-values-from-arrays) So, if you wanted to replace the blocks I show at the 21:52 mark in the video above: You could do that with these blocks: warning This could easily confuse some people if they’ve been following along in my video so please only use this new…

---

_[View the full topic](https://community.thunkable.com/t/firebase-retrieval-speed-test/1296904)._