what does "frameworkless" means for a designer?
adellava opened this issue · 1 comments
The technological choices on the code of a software produce a big impact on the user experience as they promote or make specific uses more difficult.
These choices impact on important aspects for those who contribute to the project with experience design activities. For example:
- how the user can send or receive data
- how the user will be able to use the data
- how easy it will be to change the design in the future
- how easy it will be to update the project with the possibilities offered by emerging technologies and web APIs
- how the user interface can be designed
- on the rhythm and pace of the activity
Vice versa, design activities are those that more clarify these elements.
So, in our effort to create awareness about frameworks and their impact, we think it's important to put the other experts who make decisions about the software in our discussion.
We are against a model where "everyone protects his own point of view" and acts in separate ways and times. Instead, we are in favor of making shared decisions, thinking about the good of the whole project.
I invite everyone, therefore, to contribute to this thread in order to improve the assumptions of the movement suggesting changes to the current text.