Depends what part of the design process I’m at. If I’m developing an identity, I’ll work the initial look and feel of the app alongside all the other collateral. If the identity has already been developed, then it’s a question of how well does it inform interactive elements. If I’m starting on just the “UX” of an app, I’ll be working on a whiteboard or large sketchpad to map out user journeys and flows. That’s assuming I’ve already done plenty of user research, or someone else has. At the very begging of a design, I stay away from plugins or templates because I want to feel free with as wide a solution space as possible. More on reddit.com

What kind of templates are you looking for? Both Android and iOS have community UI kits that are free to use. More on reddit.com

This does look interesting, I haven't seen a kit focused on mobile screens before. I'm mostly against using these UI kits because they are so over designed and starting a project using one feels like more work than just starting from scratch. Ie to edit one thing you need to edit a component within it, but then to edit that its built with 3 other components so you need to edit those 3, which have components within them... you see where I'm going. My suggestion would be to try to keep it as light as possible rather than just loading on more and more components for the sake of a tagline where you can say "over 10,000 customisable components". Think carefully about what needs to be a component vs just a non-component template that you can copy/paste. More on reddit.com

Are you trying to prototype full-on panning, zooming, and dynamic exposure of content depending on that panning and zooming? If so, that level of interactivity and functionality is going to be VERY difficult to prototype in figma. I am sure you could use variables to do a little bit of it but I'd suggest you look at a more advanced prototyping tool if you really want it to be a dynamic proto pulling from actual data. More on reddit.com