Thanks for your feedback. I'll leave some responses first, then give feedback on Scaffoldly below.

You're right, a lot of the issues you hit are because I haven't optimized it for mobile. I'll mostly respond to the other issues:

> trello sorta layout would work, empty cells were slightly confusing at first

People do seem to get a bit confused at first as to what the empty cells are used for. Maybe there's a stylistic change I can make (on desktop you get better warning hints if you try to interact with them in a weird way). The empty cells are there so you can a) add a new node in empty cells that are adjacent to full nodes, and b) so your selection box can have a grid to work in and you can select multiple nodes that may have empty nodes between them

> wasn't able to save text

What is your use case for saving the text? Did you want to copy and paste it somewhere? Its true that won't work. I'm going to implement c/p but within knotend so you can copy one part of a graph and paste it elsewhere. But I would need to implement a different feature to c/p from knotend into, say, text doc.

> back on Android triggered an undo?

That is intended. cmd-z/cmd-shift-z and browser history back/forward will do undo/redo.

> nav bar buttons at the top didn't seem to do anything

They are individually disabled based on the state of the graph and your selection. Probably isn't obvious on mobile.

Ok feedback on Scaffoldly...

You linked specifically to the tutorial so I'll start there. I looked on both mobile (iphone) and desktop (mac).

My initial impression is that the site is well made and nicely designed. Its easy to read.

My biggest initial hurdle was that I somewhat understood this was an infrastructure as code product, but had a hard time figuring out the details. For example, is it a custom web framework or do I bring my own framework? Does it work with many languages, and many cloud providers? How do I run this stack locally, and test it? I think it would be helpful to have a short paragraph somewhere prominent (home page, docs intro) describing those nuts and bolts early on. I think the text in your "What Does it Do?" is pretty good, but should be more granular.

I agree that AWS configuration is a pain. So the initial hook gets me to read further.

I'm not sure you need the "for Startups" in your tagline "The SaaS builder for Startups". It seems useful to anyone? Or maybe explain why this wouldn't be great for hobbyist, academic, enterprise, etc.

I wouldn't use insider terms like 'persona' in your copy, eg "Out target persona is a CTO". Even mentioning that its for CTOs is probably a bit limiting.

> Multiple Environments: Scaffoldly provisions Non-Live and Live "environments/stages"

This is really cool. This is something we hand-rolled at work previously. One challenge can be that people have different ideas of how different environments should behave, its not a one size fits all type problem.

Overall I get a sense it may address my pain points with deployment but its hard to crystalize a picture of what exactly it does. I'd like to walk away thinking "ok, I write in these languages with these frameworks and scaffoldly takes care of x,y,z". Or have a sense of comparison, like "its similar to Heroku but with x,y,z differences".

Thanks again for the feedback! Please let me know if mine was helpful or if I missed anything you wanted some eyes on.