[neya]

Cool, regardless of other commenters' advice, I think you should go forward with this. I run a dev shop and I have done this with Rails and boy, does it save you a lot of time (and thus, money). But, you should ensure there isn't a learning curve for your platform. It should be in a UI that's familiar to someone who is familiar with building their apps manually. Otherwise, it defeats the purpose. As for worrying about pixel perfect designs, don't worry about those, they're the easy part. The difficult part will be the parts that contain the majority of value for a business - the backend. Frontend is as simple us throwing in a nice UI framework and mixing and matching color themes. It is good enough and works well for most clients. The ones that require pixel perfection probably aren't your target audience as it has a lot to do with the frontend than the backend.

Contrary to popular belief, there is a lot of money in this. I sincerely wish you luck and hope you succeed.

[nickcassimatis]

Thanks. I think that's right. There are a lot of use cases where super-precise UI control is not necessary. The early web and many blogging platforms are an example where you can get very far despite some limits on UI customization.

[puranjay]

Slightly OT, but on my browser, dry.io is not on https. Big red flag for me. Chrome shows a 'Not Secure' tag for me, plus there is no favicon.

Small things but important. You might want to fix that

[nickcassimatis]

It's a good point. Our actual platform is all https. Our home page is just a static page. But you're right that it's bad optics for a platform intended to be privacy friendly to not be using https.