This content has been marked as final. Show 2 replies
I would consider actually making this into a web application in stead of a Swing or JavaFX2 application. Most if not everything is moving to the web nowadays, so if you really want to learn what you'll likely be doing out in the field, go web. JavaFX2 might be a decent bridge there if you really need some client side stuff, but I kind of doubt it.
Before you can make any choice of technology, you'll first have to get some specs sorted out. The last time I did a "proof of concept" application, I started by setting up a fictive but still realistic case; fake customer with real world requirements and limitations (budget, timeframe, even security and trust was an issue). Based on those requirements and limitations I could setup up a proper requirements document and functional specifications.
When you're at that point, it might be worth thinking about what fits the bill - including what platform or platforms to target. Even if you have client side components, I'm pretty sure you'll still have a server side component in there somewhere for example.
I agree you should SERIOUSLY consider making this Web app, mainly because of the large audience you're targeting. When you fix a bug or publish a new version of a Web app, you only have to update the code on a server. With a client app, imagine the headache of notifying 5,000 real estate clients to download & install an update!
To say nothing of the problems you face when you get a trouble call, and you have to figure out what app version your customer has. With a Web app, all users have the same version automatically.
In addition, Web apps let you add some niceties, like easily monitoring (on the server!) which program features are used most often, etc.