Prioritize the form engine, but make the form UI flexible

[sedwo]

I can empathize with your effort to build a form engine as I've done it before across two different products, and tried nearly every other type of iOS forms framework in the last 10 years, and support its powerful tech.

My kind request and hopeful guidance is to prioritize your efforts on the form engine data and architecture, in a way to abstract it with then simply allowing extensions to something like Eureka to build the form UI and allow people to customize it.

It's challenging enough to create a powerful forms framework with eventual rules and field dependancies, without the UI getting in the way. Take some notes from hyperoslo's Form engine.

I will watch this repo and experiment with your project to see if it fits my upcoming app idea.

Good luck!

p.s. Cocoapods support would be a nice benefit. : )

[VicFalcetta]

First, thanks for your comment, we may have seen after sometime due to my new job, it really made me happy! It was our first time creating a framework and we are still learning some aspects of creating a open-source tool.

We will take some look on the material and references you provided for us and try to work on improving it! Also we will look into providing cocoapods support!