Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify prototyping of apps #8621

Closed
4 of 6 tasks
nkylstad opened this issue Jun 10, 2022 · 2 comments
Closed
4 of 6 tasks

Simplify prototyping of apps #8621

nkylstad opened this issue Jun 10, 2022 · 2 comments
Labels
area/data-modeling Area: Related to data models - e.g. create, edit, use data models. area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. Epic Used by zenhub to identify the epics that group issues. solution/studio/designer Issues related to the Altinn Studio Designer solution. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design.

Comments

@nkylstad
Copy link
Member

nkylstad commented Jun 10, 2022

Description

Current situation when developing apps is that developer must have data model ready BEFORE starting app development. All form fields must be connected up to a data model field for the form to render. In addition, all testing of a form and how it looks/feels must be done locally, making a disconnect between developing the form in the Studio Ux Editor, and actually testing and updating. This results in a lot of prototyping having do be done by manually changing the config files.

This issue aims to address this, and to give an overview of which specific issues need to be solved in order to improve the app developer experience when it comes to rapid and simple prototyping.

In scope

Out of scope

Oher tasks that are related/would improve the app developer experience

Additional Information

For rendering forms in apps without a set/predefined data model, there are a few options.

  • Treat all fields without data model binding as helper fields, with no explicit data model for helper fields
  • Treat all fields without data model binding as helper fields, and generate a separate data model for helper fields
  • Autogenerate data model based on UI model, and use this all the way (or replace with permanent model once it is defined)
  • Complete separation of UI model and data model. Mapping of data from UI model to data model f.ex. on submit, or when application owner fetches the data.

Tasks

@nkylstad nkylstad added area/data-modeling Area: Related to data models - e.g. create, edit, use data models. area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. solution/studio/designer Issues related to the Altinn Studio Designer solution. Epic Used by zenhub to identify the epics that group issues. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. solution/app-frontend labels Jun 10, 2022
@nkylstad nkylstad removed this from Data modelling Oct 7, 2022
@FinnurO
Copy link

FinnurO commented Jan 12, 2023

@nkylstad nkylstad moved this to 📈 Todo in Team Studio Jan 16, 2023
@nkylstad nkylstad removed the status in Team Studio Feb 26, 2023
@nkylstad nkylstad moved this to 📈 Todo in Team Studio Aug 7, 2023
@nkylstad
Copy link
Member Author

nkylstad commented Aug 7, 2023

This is really more of a roadmap issue, and most of the issues with prototyping of apps are solved by the basic preview that has been implemented in Studio. This allows users to create and view their forms before having to start working with the data model, which was the background for this issue.

Closing this issue.

@nkylstad nkylstad closed this as completed Aug 7, 2023
@github-project-automation github-project-automation bot moved this from 📈 Todo to 🧪 Test in Team Studio Aug 7, 2023
@github-project-automation github-project-automation bot moved this to Ready for dev in Design Altinn 3 Aug 7, 2023
@nkylstad nkylstad moved this from 🧪 Test to ✅ Done in Team Studio Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/data-modeling Area: Related to data models - e.g. create, edit, use data models. area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. Epic Used by zenhub to identify the epics that group issues. solution/studio/designer Issues related to the Altinn Studio Designer solution. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design.
Projects
Status: Done
Archived in project
Development

No branches or pull requests

2 participants