61–70 of 82 posts
it's really just for Angular2? which is overly complex for many. I'm using vue which has different similar frameworks.
Earlier quoted context omitted.
I don't believe I ever mentioned ionic v2... I don't doubt v2 brought many improvements. However you just can't beat the power of not operating in a Webview.
However, Webviews do give you a very predictable container to target. If you use something like Intel Crosswalk [1] as part of your project for Android, you can bundle a recent Chromium webview to much older devices. And Flexbox is very well suited to solve phone/phablet/tablet layout problems. [1] https://crosswalk-project.org/
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 nat…
> 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.
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.
What astounded me most was that nearly none of the established solutions offers a simple way to just cache these requests until when the device is online or any other simple ways to get such basic stuff working when offline/the connection is bad.
Generally speaking: In early 2017 its still way to hard to get very basic stuff on native (let alone web based) mobile apps working offline. The whole offline-first movement still has a lot of educational work to do.
We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova plugin space. This, of course, is not the fault of the Ionic team, but it does create a frustrating development experience that played a large part in us abandoning it as an option. This was also our f…
About to embark on a potentially large Ionic project. What were some of the issues that you had?
The lack of any kind of commercial support is real and frankly that is the largest issue that you will have to deal with. I have searched high and low for any kind of commercial support that I can offer my customer. I am it. Or somebody like me.
However, I will say that in two years of using Ionic I have never had to modify one Cordova plug-in or any native code in order to release my apps. I do mess around with the native code sometimes but usually on an exploratory mission. Other than that, my biggest issue so far has been with how quickly ionic and Cordova get updated and how quickly my code gets out of date because of that. Then when I have to update I have to make sure that nothing breaks by writing all sorts of tests or doing manual testing yada yada yada. Also getting answers from support or anybody qualified is sometimes difficult and you have to wait days or just figure out your own work around.
At the moment we are in the process of evaluating different frameworks/solutions to build a simple native App for iOS and Android. Its mostly some basic forms to build simple objects that eventually get posted to a JSON API. What astounded me most was that nearly none of the established solutions offers a simple way to just cache these requests until when the device is online or any other simple ways to get such basi…
I ended up using Firebase and it handled that case just BEAUTIFULLY right out of the box; the data updates optimistically on the player's own device, and once a connection is established Firebase syncs it with the datastore and all other phones update accordingly.
I would say that this is some pretty sophisticated behavior that I, the developer, just used right out the box following documentation.
We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova plugin space. This, of course, is not the fault of the Ionic team, but it does create a frustrating development experience that played a large part in us abandoning it as an option. This was also our f…
At the moment we are in the process of evaluating different frameworks/solutions to build a simple native App for iOS and Android. Its mostly some basic forms to build simple objects that eventually get posted to a JSON API. What astounded me most was that nearly none of the established solutions offers a simple way to just cache these requests until when the device is online or any other simple ways to get such basi…
Disclosure: I work on Ionic Ionic 2 is much more performant and scales much better for app development than Ionic 1. I have yet to meet anyone who has not really enjoyed developing Ionic 2 apps. We take a tremendous amount of pride in the developer experience! Native apps will always be a little faster but if you can get 60FPS either way, who cares? Ionic is easier to build apps with, and developing in the browser is…
Well unfortunately ionic2 is super slow to develop.. Ionic1 is nice in the beginning, but if your app grows, you're simply waiting and waiting. This is a problem with all javascript frameworks.. just 'watch' a directory for changes and restart, recompile everything