3 ms·

Not long ago I was an Ionic believer, but not anymore... the lack of support for their cloud services [0] has turned many people off and signals that they don't

by joeyspn 10y ago

Not long ago I was an Ionic believer, but not anymore... the lack of support for their cloud services [0] has turned many people off and signals that they don't mind leaving their users "locked". Devs are migrating en masse to react native. I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy Ionic 1.x/Angular projects, while the codebases are migrated to react native... For hacking quick MVPs is not bad, it was even cool 2 years ago, but for serious projects starting from zero, react native is a smarter choice. [0] https://github.com/driftyco/ionic-cloud/issues https://github.com/driftyco/ionic-cloud/issues

jordache 10y ago
why use the cloud though? just build on premise and use existing MDM, or App Store
- jawarner 10y ago
  Right, AFAIK the framework itself functions independently of the services, so you can drop in whatever solution you want for push notifs / analytics / MDM.
  - dante_dev 10y ago
    that is what we do in our organization, we don't see value on their cloud services, we see value on their framework
    - jordache 10y ago
      Bingo! for hybrid development, I don't see anything better out there than ionic. Key point - for hybrid development. There are a lot of use cases where hybrid mobile apps are appropriate (CRUD). With ever more powerful devices, the argument for hybrid increases.
- cyberferret 10y ago
  Exactly. You don't NEED to use Ionic's cloud platform. You can develop an app completely independent of it, or else integrate with other back end services. Personally, I've developed Ionic apps that integrate with Firebase, PushWoosh, Back& among others... You are free to choose. No lock in necessary.
marvindanig 10y ago
> I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy… It's better to not have such people working for you in the first place. Maintaining existing software to focus on real business is just the kind of founders I'd want to work with. It's a part of being a part of a startup, and those who jump the ship too often do not leave any legacy behind.
- brogrammernot 10y ago
  Thank you. Developers who jump because they'd rather build from scratch instead of helping maintain and improve an existing solution is irritating. More power to them, but I respect developers a lot more who stay, fight through legacy code battles, make steps/headway to shift the application to a newer platform that makes practical sense than those who leave. If your employer refuses to move to a stack you feel is justifiably better, in both business and technical aspects, then I totally understand leaving. If you're leaving because you don't want to maintain a system that's "older" and don't want to take on the challenge of improving it then I agree with your post. I'd rather not have those developers to begin with.

by joeyspn 10y ago

jordache 10y ago

why use the cloud though? just build on premise and use existing MDM, or App Store

jawarner 10y ago
Right, AFAIK the framework itself functions independently of the services, so you can drop in whatever solution you want for push notifs / analytics / MDM.
- dante_dev 10y ago
  that is what we do in our organization, we don't see value on their cloud services, we see value on their framework
  - jordache 10y ago
    Bingo! for hybrid development, I don't see anything better out there than ionic. Key point - for hybrid development. There are a lot of use cases where hybrid mobile apps are appropriate (CRUD). With ever more powerful devices, the argument for hybrid increases.
cyberferret 10y ago
Exactly. You don't NEED to use Ionic's cloud platform. You can develop an app completely independent of it, or else integrate with other back end services. Personally, I've developed Ionic apps that integrate with Firebase, PushWoosh, Back& among others... You are free to choose. No lock in necessary.

marvindanig 10y ago

> I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy… It's better to not have such people working for you in the first place. Maintaining existing software to focus on real business is just the kind of founders I'd want to work with. It's a part of being a part of a startup, and those who jump the ship too often do not leave any legacy behind.

brogrammernot 10y ago
Thank you. Developers who jump because they'd rather build from scratch instead of helping maintain and improve an existing solution is irritating. More power to them, but I respect developers a lot more who stay, fight through legacy code battles, make steps/headway to shift the application to a newer platform that makes practical sense than those who leave. If your employer refuses to move to a stack you feel is justifiably better, in both business and technical aspects, then I totally understand leaving. If you're leaving because you don't want to maintain a system that's "older" and don't want to take on the challenge of improving it then I agree with your post. I'd rather not have those developers to begin with.