I found it faster to publish the site and check the custom code results than previewing it on the @webflow designer. This compiling custom code loader runs forever. Hey @leinwand, can we please make it faster?

I need to host a single page with some HTML/CSS/Javascript (all inline...no external files). What's the easiest way to just copy/paste and have a publishable URL I can share of that with folks?

Excited to release a roundup of @Versoly today but was reminded of something i'll mention in the episode. It's crucially important to observe someone using your tool/website/app. Especially if they are non-technical. While using this stuff seems perfectly 'normal' and natural to us people who don't have these technical proficiencies will use your app in completely new ways. This not only allows us to rethink the UX but also they will uncover bug you would not have found otherwise. Please try and make time for testing and if you can, observe them use it.

Yesterday I shared some semi controversial thoughts on the state of talent in #nocode. Here's what I'm seeing in our industry: - the majority of Flywheel applicants aren't qualified to build basic or introductory applications - every month we get 2-3 project requests where the client has been abandoned by their previous freelance developer - in addition to those we get 2-3 requests where they have a product that doesn't work. Usually a combination of bad DB design and totally misunderstanding the client's requirements - about 30% of our job applications have frequent misspellings and/or misspell my name - we've had job applicants claim our templates as their own projects in their portfolio🤦 I want to be really clear, this is a disaster at the bottom level of nocode. It doesn't affect the top end. The majority of the companies and clients we work with have processes and budgets that allow them to escape this. At the bottom end, in particular, with clients who are individuals and new to software development, they're frequently hiring developers who aren't going to be able to deliver. This isn't everyone, of course. There are good devs out there. But bad devs reflect negatively on all of us. At Flywheel, it's bad enough that we don't hire nocode devs anymore! We target traditional devs and university grads. We've had a significantly better experience teaching them the platforms than finding someone who's "well versed" on it. How do we solve this? I don't have an answer. It's just really a shame because there are too many people passing themselves off as experts but aren't qualified. I'd say half of the "bad" projects we see come from someone who's listed on the expert forum of a platform. I think that nocode's accessibility is a double edge sword. By allowing anyone to become a developer, you've done exactly that. What I'd really like to see: - platforms significantly increase expert standards and their review process. - more emphasis on studying traditional development skills (guess what! designing a DB schema in nocode is the same as code) - clients should be more aware of how to qualify devs. I don't think this will happen, but I do wish ppl were smarter to maybe challenge if you're really going to get the app you want for $5k (it's probably too good to be true) To be explicit. I don't want to discourage anyone from becoming a nocode developer. This is a life changing opportunity for a significant portion of the world. What I want to see is more structure, professionalism, and and emphasis on building high quality software (not cheap software). That benefits all of us and helps grow the ecosystem. If nocode can't deliver quality software, the ecosystem will lose its credibility which is difficult to overcome. Anyways, just some thoughts from my side!