That depends on whether you want the users to access via HTML or custom
networking.

Usually it is better to map out the user experience first, then figure out
which approach best supports that experience, than to work it the other way
'round.

In principle, once you have figured out exactly how the application should
behave, both logically and interactively, then you can implement a common
business logic foundation and layer different front ends onto it. That way you
could have both a Swing-based application and a Web app for the same
functionality.

- Lew