All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
There are some functions that only Mappers should see, and some functions that Developers should see.
One idea is to just commit to building two seperate screens so that we can purpose build a screen dedicated for FIELD MAPPERS to do the mapping without worrying about hiding or disabling features that a Developer should do.
Likewise when a Developer is reviewing and implementing the Mappings as RULES - they probably have a different set of Fields and Function that would make that task easier.
This has aspects of Functionality, Design, and probably a big Technical Impact - so more work required to figure out the pros / cons to splitting this.
John Munkberg
I think this is actually needed, but comes with the overhead of more clicks when the mapper is the developer, so we need to ensure is intuitive and easy to get to for the combined role.
Attachments Open full size