You have done need finding research, presented your findings with your customers, and reviewed any changes to the requirements that may arise from the presentation to your customers.
Instead of starting with a paper prototype or the “back of a napkin” sketch, we will be using Figma. At this stage of the design, we are focusing on a prototype of the application to identify the layout, navigation, and presentation of information/features. You don’t need to worry about the visual “style” or aesthetics at this point (you can do that with your GUI framework of choice later) so you may use placeholder images and textual content (lorem ipsum). Your prototypes should have basic interaction to transition from screens and show common controls to indicate the presence of your application features (navigation menus, buttons, switches, option buttons, textboxes, etc.) as appropriate.
This prototype will not be “fully” interactive. For example if you make a website where people can shop for goods online and put them in a cart, you might have a menu item for a specific category you want to show. In the list of all category items, you might have one that is interactive via click to demonstrate adding the item to the cart. While you won’t be able to simulate text entry, and persistent data across screens, you can simply show the controls and subsequent screens (payment options, shipping, checkout, etc.) and allow the user to see the controls and navigate through the screens.
You can look through figma community projects for ideas, but make sure that your project is uniquely yours and fits your particular domain/application.
While creating your prototype, think about our RSME readings and how you would do a usability study with your prototype.
prototype in your dev team GitHub repo