Web Dynpros will perform better, transaction iViews use webgui (ITS) behind the scenes. Of course if your application has to be accessible to SAP GUI users as well, then you should take the classic dynpro route. I suggest you implement the functionality in a way that you can easily access it from either UI, e.g. use ABAP classes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.