jelnur

Thanks for feedback. I just included it as a picture, but you're right.

It's included only as a picture :)

> That is the very definition of a waterfall design model.

No it doesn't mean that. When you can rely on your data it's easies to code and test than when you have to account for every bad data combination.

And remove the constraint is easier when you need it, than to add it later.

Thanks for the feedback!

Yes, the focus now is to validate the concept and make an easy-to-use and flexible product

Thanks for your valuable feedback! Yes, you're right. But for now I choose to make the product exceptionally easy and flexible (even with manual data entry). Automation can be added later, after concept is validated.

You are right. We'll add Import data and also expose API to automate this task