In this video, Emmanuel Henri defines the objectives of the project that is tackled throughout this course.
- [Instructor] When you build a new application, design or prototype, it's important to define what objectives you have and turn them into stories for development. Usually this exercise is done with the entire team of developers, designers and stakeholders. In some cases, you want to involve potential customers or users of your application. So let's say in our project here we want to build a new IT asset management tool where we have three screens, one that allows us to manage our users, one to manage our assets, and a third one to connect these assets to our users.
The first screen which is the user screen we want to be able to add, delete and modify new users and we want to be able to do this in a user-friendly way. The second screen is where we can add assets like computers, network routers, servers, databases, et cetera. Again, for this screen, we want to be able to manage these assets. And finally in the third screen, we want to be able to connect our assets with specific users, an IT management tool where we connect both.
So in summary, we have a list of these objectives which if you are using agile would also translate it to stories for designers and developers to build from. So the list looks this. I want to add new users. I want to modify users. I want to delete users. I want to add new IT assets. I want to delete IT assets. I want to add connections in between assets and users. I want to modify the connections in between assets and users. Although we won't be covering all items in this list, with the design and prototype, we'll get started on a few of them.
But this gives us an overview of the main objectives of the application.
- Defining your objectives and UX stories
- Designing the user management tool
- Importing assets into Framer
- Creating flow between screens
- Adding interactions, micro-interactions, and animations