Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "ionic2"
JS gets a lot of hate lately.
The last month I was developing a mobile app that just showed information. I have to say ionic2 was quite good for it. Sure it's not native but I think it's a good thing for some apps13
“Fullstack dev continues to be consistent”
We’d an enhancement request where we needed to support Ionic apps. Our manager didn’t know anything about Ionic so she asks us what it was instead of asking Google.
Manager: so what’s this Ionic thingy?
Me: Ionic issss.... (gets interrupted by Fullstack dev)
Fullstack dev: so the thing is ... it’s like... (consistent with his opening lines as always) it’s a third party plugin which converts react app and html pages to native code.
Me: (thinking of sacrificing him at the altar of Lucifer)
More to come.18
Best way to make cross platform apps (iOS + android)?
I've heard that the following are good options:
I have experience in web development but I am a quick learner and don't have a problem learning a new language.
Or should I go native and release apps for the different systems separately?25
Do you plan to develop a mobile app which works cross platform? DONT USE IONIC(2). JUST DONT. Thank me later. Have a look at react native (not perfect but much better)13
Ionic be like: Testing? Fuck that lets just bring out ionic 3.0 beta and let our testing example repo die with a few pull requests from one dude who actually tries to keep it updated
I'm starting with native mobile development to create an app with a lot of potential.
Since I didn't know a lot about this field (being a full stack web developer) I started doing some research about what technologies I should choose.
The app, having the need to be cross platform, I needed a cross platform toolkit. Although the app could make a move on to truly native code (Swift + Java), it would take a long time; hence I would require a faster short term solution.
The best option was Xamarin (for native code). However, due to certain app requirements, I would have to write a lot of platform specific code; defeating Xamarin's purpose.
The next option was a hybrid mobile app. Ionic2 was the best option here but I don't like ng-2.
In the end I came upon the realisation that a web-app was the only true cross-platform solution.
As I delved deeper into mobile app development, I found out that the webstack lacked a lot. My conclusion was, that for a truly great (cross platform) experience, we need to improve the web domain.
HTML elements can become better (more XAML like). A native templating API, to forgo the need for libraries like ReactJS or VueJS.
Better layout models. Flexbox is good but can improve. CSS should be more like Sass/stylus.
NOTE: These are just my opinions and I'm probably wrong in many places so forgive me.1
Creating a script that switches a global node_module package version (because we have legacy projects mixed with normal ones)
Whats yours opinion on Ionic2 for mobile development, and Electron for desktop apps. Any good or should we stay away?2
Ionic2 + pouch DB seem to be a good choice ... No I sit her 8 hours and try to get a database access fml
Has anyone ever worked with a NativeScript Angular project? If so, how do you feel that they compare to regular Angular2+ webapps or to Ionic2+ mobile apps from a code writing and ease perspective? I just started working with Ionic2+ and they blew me away with the ease of code and how quickly you can get things running and how well and native they do look and act, however the user experience can't compete with that of Xamarin or ReactNative apps. I've also worked with just Angular2+ as well for particular apps and I can't say it's a bad experience because frankly it's one of the best pure web tools I've ever worked with.
Had to refractor and abstract some code into an angular 2 component so it can be reused by another. Well I could have just copied and pasted the code from component 1 to 2, that would have been a lot more faster than making this piece of code separate. The later is better, removes code duplicate and your code reads better.