Hacker News Reader

Comment by AlexC04 | Hacker News Reader

I'm leading a small team in building an ionic app right now.

The edge that cordova/phonegap/ionic will retain is the HTML and CSS part. As well as, at least for a little while, a more robust plugin ecosystem. Though that second one will change VERY rapidly.

The other developers on my team are very much frontend & CSS types.

I would be too much of a bottleneck if I were the only developer able to write the code for the app.

If xamarin were free when I started, I may have given it more time in evaluation, but at the end of the day, I think that the choice would have remained ionic.

Even react-native isn't ready yet if you're a windows based shop. But maybe that's come along in the last couple months too.

View on HN

> Even react-native isn't ready yet if you're a windows based shop.

Don't forget, Facebook's annual developer conference F8 is coming up next (April 12th 2016). They will surely have some new announcements in a few weeks.

True! And as I realized in another thread... Having an Ubuntu space on Windows actually makes "native" react-native totally plausible.

I'm practically in the exact same boat as you and also using Ionic. The only thing I can think of to make me consider migrating is performance. Cordova/Ionic can be slow to handle complicated screens, animations and transitions.

Getting native performance would be a big differentiator. Hopefully, Ionic/Angular 2.0 will go a long way to improving performance.

I can sympathize! I'm using an encrypted database on the device and there are some real slowdowns.

For as far as I trace the code, the only part I can't really optimize is the db open commands

For the most part it's pretty slick, but I can still feel it. It could be faster.

One database trick I used was to pre-select queries in the background and cache the results. It creates some code overhead for updating/inserting that has to keep the cache in sync. However, it simplified the logic in the rest of the code because I didn't need a promise for a select, I just read the cached object. That allows me to outsource the controllers for screens to developers who don't have to work with promise overload. They access my wrapper service for the content using synchronized code.

My database is also very simple. If you have a complicated schema with lots of joins, it'll be tough to cache things and keep it in sync with the db.

Feel free to email me, if you want more details on this concept.

Reply on news.ycombinator.com