I found this closed topic asking the same thing. It was custom collection under custom collection. Which official response is to workaround for the time being.
I tried to have list collection nest under custom collection, it did work as shown below
Apologies for a lack of response from the Retool team. Nested collections have not been on the mobile roadmap and barring any change won't be on the mobile roadmap.
@neilbalthaser I noticed you have commented on several mobile app threads, after chatting with our engineering team we are likely going to be moving resources away from our Mobile app to better focus on our core product.
If you can share with me details on your use case and what kind of app you are looking to build, I can help to better understand how to help you. If you are needing a Retool app for mobile devices, you may need to build out a web app and set it up for use in mobile browsers.
Let us know what you are trying to accomplish and we can best help to assist you in finding the tools to do so
That’s unfortunate. Does that mean you are going to stop supporting mobile apps? What does that mean for those of us who have invested considerable time and effort on building out a mobile app solution using the Retool platform? Are you advising that we stop further development or shift resources elsewhere? Some additional visibility and advice would be great appreciated.
We will continue to support mobile apps, we just don't be releasing new features. We will be maintaining current functionality and fixing any regressions that appear. We have some of outstanding bugs and feature request tickets that likely will not see any progression the near term on.
Given our focus on Retool Assist for using prompts to build apps, I would recommend using Assist to build mobile responsive web apps to use in mobile browsers instead of building in the Retool Mobile app when developing new projects. As Assist can best leverage our components and settings to build and iterate quickly.
If your app works as needed then there is no need to change anything, but I just want to ensure that expectations for fixes and changes to be inline with what our team is able to do going forward.
Using development assistants is a growing trend, but the problem lies in the limitations of using a web browser. Applications that work offline can't be developed, nor can file export capabilities be utilized. I maintain that the market niche is mobile devices, and I don't understand how the development team can remain disconnected from the reality of mobile application demand. I hope they at least consider the demands of users who have been using the platform for their work with already deployed applications and at least complete the cycle of what has already been requested.
