I'd disagree strongly. The dynamics of a web application are different than a terminal app.
You're average web-skinned 3270 app is generally a direct translation of whatever the app did done by a gang of contractors without any design consideration.
The problem with that is that for all of the most trivial of apps, the use cases were envisioned 30 years ago. That's usually a problem. For example, one app that I looked at that still had old documentation available. Their design was based around 90% of transactions were initiated by a clerk opening paper mail. The obtuse layout of screens was there because they processed mail to dispatch it to appropriate teams of clerks, and it was customized to each function. Today 90% of transactions are initiated by phone or webchat, and are expected to be resolved in one call.
Bad web implementations are common. But it's almost always bad to ape things that aren't understood, which is the case 80% of the time for webified temrinal apps.
You're average web-skinned 3270 app is generally a direct translation of whatever the app did done by a gang of contractors without any design consideration.
The problem with that is that for all of the most trivial of apps, the use cases were envisioned 30 years ago. That's usually a problem. For example, one app that I looked at that still had old documentation available. Their design was based around 90% of transactions were initiated by a clerk opening paper mail. The obtuse layout of screens was there because they processed mail to dispatch it to appropriate teams of clerks, and it was customized to each function. Today 90% of transactions are initiated by phone or webchat, and are expected to be resolved in one call.
Bad web implementations are common. But it's almost always bad to ape things that aren't understood, which is the case 80% of the time for webified temrinal apps.