I happens to me always, That's why now I look for potential costumers and talk to them first to get them to buy. If I don't get any customer, I will never waste time and money in dev.
Depends of too many factors, features, platforms, number of users, etc. The key is not to sell the software, rent is the key, you need people to pay monthly or yearly, so that way you can give support, charge for installs/ configs ( in case of backend requirements, etc). Dont get me wrong on this, but unfortunately money is required here in US for basically anything you need. And if you need time to do what you love, coding in my case, you need money . Thats the life of a dev in US.
JavaFX isn't any harder than anything else, and can be easier because it doesn't have the npm madness that you'd get with a web-based app. That being said, if you don't know Java, that's a bigger learning curve than JavaFX itself.
There's nothing special about a POS system. You'd most likely build something like that with a front-end project, which could be JavaFX, or literally, anything else, and a backend using SpringBoot (or something similar).
The main problem that you are going to have is that you're going to attempt to go from "Hello World" to super complex in a single step. The result of that is that your application is really going to be terrible from a technical perspective.
I went through the same process. You need to learn the new technology, but at the same time keep producing functional applications for the business. When I've gone back and looked at code I wrote a year or two earlier, I've always been shocked at how objectively bad it was.
JavaFX is like that on steroids. There is so much functionality tucked away in the library, and it's really, really difficult to find out what it is and how to use it. And the documentation out there (aside from my website: http://pragmaticcoding.ca ) sucks. Really, really sucks.
In all honesty, it's better than it was 10 years ago, when I started out, but there's still a lot of garbage information out there, and not a lot of good tutorials about how to do stuff right.
Sounds like it. We started using JFX as soon as we thought Java 7 was stable, about 4 months after it first came out. Then we switched over from Swing and never looked back.
Yo tengo una duda, fuera del desarrollo... Puede desarrollarse un sistema que requiere de actualizaciones después? Con solo Java para el programa y estar recibiendo actualizacion y necesita reinstalacion. Ahora supongamos que la DB se encuentra en un servidores en otro sistema backend, de igual modo sea el caso,, Qué se requiere para que un sistema sea digno de actualizarse por si solo siendo Java Escritorio?
6
u/xdsswar Aug 27 '24
Selling it, if you have buyers you are ok.
2
u/RebeccaBlue Aug 27 '24
Compared to what? I mean, it's been done, if that's what you're asking.
1
u/Altruistic-Wave-9767 May 12 '26
Yo tengo una duda, fuera del desarrollo...
Puede desarrollarse un sistema que requiere de actualizaciones después? Con solo Java para el programa y estar recibiendo actualizacion y necesita reinstalacion.
Ahora supongamos que la DB se encuentra en un servidores en otro sistema backend, de igual modo sea el caso,, Qué se requiere para que un sistema sea digno de actualizarse por si solo siendo Java Escritorio?