I don’t see why not. Some things are to keep in mind:
Try to keep the Weblow exported files untouched, so you can continue to design in parallel and updates are easy.
Use the Custom Attributes in Weblow to add dynamic content to your WF pages.
Don’t use interactions with onScroll events, they’re being deprecated on mobile.
UIWebView is not Safari… So a webapp through “add to homescreen” or with Uiwebview on a native shell aten’t the same, eventually.
The last one is a oersonal belief: prefer building a bottom menubar a-la Facebook rather than using hamburger icon dropdown menu. Hamburger menus aren’t well perceived as menu by users, has been proven many times.
I’ve also tried adding that code as an HTML embed but the result was collapsed on one line and the > was still escaped:
(this strikes me as a bug)
Maybe Webflow can be used to get started with a layout for a web app, or to build pieces in a WYSIWYG way and export them (them manage the code manually) but I don’t think it’s designed for iterating through a realistic development cycle (“Try to keep the Weblow exported files untouched”).
I’m not quite getting everything. Making a web app and making templates that will become dynamic later are two topics.
I make templates with webflow, for both websites and apps. We usually add the dynamic info we need in Webflow by adding custom fields. Look for custom fields in Webflow, add them to some of the elements you want to render dynamic, see what effect it has on the code and talk with the developers to see how they can work with that.