on 07-13-2016 6:10 PM
Hi experts,
what do you think in general, would it be advisable to redesign around 60 existing custom Webdynpro screens (mainly tables/ALV grids, with a lot of searching and filtering) and build Fiori apps instead?
I have the feeling that only chaning the UI to Fiori won't increase the User Expierence without making the screens more simple, but this would involve to create a huge amount of task based Fiori apps to cover all existing functionality of the custom Webdynpro screens.
Do you have any expierence on that kind of redesign projects?
Cheers,
Wladimir
Hi Wladimir
Questions that I would have in your situation that will help in making a decisions are questions like these:
Normally the priority for investment is based on return on investment and I would be surprised if a project of rebuilding these apps into new technology, with the same features and same device (PC) would be the project with the highest ROI. What I would look and analyse is a subset of users that are perhaps only using a subset of the apps and focus on those. Sometimes users dont know what they need but they do know what gives them problems in their day to day work so running workshops to discover that would be a good starting point regardless of whether you go further with the migration of the apps or not.
What you describe as the scope of the apps sounds like something that an experienced Fiori developer could do rather quickly. Viewing data is easy with Fiori, creating, changing etc. is where things get more complex and expensive. Good luck..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.