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 - "reactnative"
You know what?
Young cocky React devs can suck my old fuckin LAMP and Objective-C balls.
Got a new freelance job and got brought in to triage a React Native iOS/Android app. Lead dev's first comment to me is: "Bro, have you ever used React Native".
To which I had to reply to save my honor publicly, "No, but I have like 8 years with Objective-C and 3 years with Swift, and 3 years with Node, so I maybe I'll still be able help. Sometimes it just helps to have a fresh set of eyes."
"Well, nobody but me can work on this code."
And that, as it turned out was almost true.
After going back and forth with our PM and this dev I finally get his code base.
"Just run "npm install" he says".
Like no fuckin shit junior... lets see if that will actually work.
Node 14... nope whole project dies.
Node 12 LTS... nope whole project dies.
Install all of react native globally because fuck it, try again... still dies.
Node 10 LTS... project installs but still won't run or build complaining about some conflict with React Native libraries and Cocoa pods.
Go back to my PM... "Um, this project won't work on any version of Node newer than about 5 years old... and even if it did it still won't build, and even if it would build it still runs like shit. And even if we fix all of that Apple might still tell us to fuck off because it's React Native.
Spend like a week in npm and node hell just trying to fucking hand install enough dependencies to unfuck this turds project.
All the while the original dev is still trying TO FIX HIS OWN FUCKING CODE while also being a cocky ass the entire time. Now, I can appreciate a cocky dev... I was horrendously cocky in my younger days and have only gotten marginally better with age. But if you're gonna be cocky, you also have to be good at it. And this guy was not.
Lo, we're not done. OG Dev comes down with "Corona Virus"... I put this in quotes because the dude ends up drawing out his "virus" for over 4 months before finally putting us in touch with "another dev team he sometimes uses".
Next, me and my PM get on a MS Teams call with this Indian house. No problems there, I've worked with the Indians before... but... these are guys are not good. They're talking about how they've already built the iOS build... but then I ask them what they did to sort out the ReactNative/Cocoa Pods conflict and they have no idea what I'm talking about.
Well, one of these suckers sends a link to some repo and I find out why. When he sends the link it exposes his email...
This Indian dude's emails was firstname.lastname@example.org...
We'd been played.
Company sued the shit out of the OG dev and the Indian company he was selling off his work to.
I rewrote the app in Swift.
So, lets review... the React dev fucked up his own project so bad even he couldn't fix it... had to get a team of Indians to help who also couldn't fix it... was still a dickhead to me when I couldn't fix it... and in the end it was all so broken we had to just do a rewrite.
None of you get npm. None of you get React. None of you get that doing the web the way Mark Zucherberg does it just makes you a choad locked into that ecosystem. None of you can fix your own damn projects when one of the 6,000 dependency developers pushes breaking changes. None of you ever even bother with "npm audit fix" because if security was a concern you'd be using a server side language for fucking server side programming like a grown up.
Mine are still working.35
I'm 54 y.o.
I do understand software development, agile, web application development, linux server, basic/moderate AWS skills, etc.
Now they laid me off instead of including me in the evolution of version 2 of the software. Maybe covid, company had almost no cash-flow. Well they have now...So basically they fired me to find money to rewrite the application.
I feel without hope at my age.
I'm a generalist.
I can understand fairly well everything you'll throw at me, reactnative, angular, nosql, python, but I have little first-hand experience.
I don't have a lot of management skills, even if I've given frequent presentations to C-roles and board, and I implemented a whole agile methodology in my team.
I don't know what to do.
The amount of technology to study is huge nowadays. When I was younger I could get away with some php and java.
Full-stack developer is a big word for me. Maybe I could handle a full stack web application, but not from scratch.
I feel at my age, I'll compete with 20-something guys with better skills and lower salary requests.
I don't think I can pull a night anymore.
I'm trying to shoot high to management positions with no much success.
I'd like to go on developing, I know that there are 50-something developer out there, but who managed to find a new position at 55? at 60?
As soon as I finish the few money I spared, I'll be on the street, I'l be the "website for food" guy.62
I have been a mobile developer working with Android for about 6 years now. In that time, I have endured countless annoyances in the Android development space. I will endure them no more.
My complaints are:
1. Ridiculous build times. In what universe is it acceptable for us to wait 30 seconds for a build to complete. Yes, I've done all the optimisations mentioned on this page and then some. Don't even mention hot reload as it doesn't work fast enough or just does not work at all. Also, buying better hardware should not be a requirement to build a simple Android app, Xcode builds in 2 seconds with a 8GB Macbook Air. A Macbook Air!
2. IDE. Android Studio is a memory hog even if you throw 32GB of RAM at it. The visual editors are janky as hell. If you use Eclipse, you may as well just chop off your fingers right now because you will have no use for them after you try and build an app from afresh. I mean, just look at some of the posts in this subreddit where the common response is to invalidate caches and restart. That should only be used as a last resort, but it's thrown about like as if it solves everything. Truth be told, it's Gradle's fault. Gradle is so annoying I've dedicated the next point to it.
3. Gradle. I am convinced that Gradle causes 50% of an Android developer's pain. From the build times to the integration into various IDEs to its insane package management system. Why do I need to manually exclude dependencies from other dependencies, the build tool should just handle it for me. C'mon it's 2019. Gradle is so bad that it requires approx 54GB of RAM to work out that I have removed a dependency from the list of dependencies. Also I cannot work out what properties I need to put in what block.
4. API. Android API is over-bloated and hellish. How do I schedule a recurring notification? Oh use an AlarmManager. Yes you heard right, an AlarmManager... Not a NotificationManager because that would be too easy. Also has anyone ever tried running a long running task? Or done an asynchronous task? Or dealt with closing/opening a keyboard? Or handling clicks from a RecyclerView? Yes, I know Android Jetpack aims to solve these issues but over the years I have become so jaded by things that have meant to solve other broken things, that there isn't much hope for Jetpack in my mind 😤
5. API 2. A non-insignificant number of Android users are still on Jelly Bean or KitKat! That means we, as developers, have to support some of your shitty API decisions (Fragments, Activities, ListView) from all the way back then!
6. Not reactive enough. Android has support for Databinding recently but this kind of stuff should have been introduced from the very start. Look at React or Flutter as to how easy it is to make shit happen without any effort.
7. Layouts. What the actual hell is going on here. MDPI, XHDPI, XXHDPI, mipmap, drawable. Fuck it, just chuck it all in the drawable folder. Seriously, Android should handle this for me. If I am designing for a larger screen then it should be responsive. I don't want to deal with 50 different layouts spread over 6 different folders.
8. Permission system. Why was this not included from the very start? Rogue apps have abused this and abused your user's privacy and security. Yet you ban us and not them from the Play Store. What's going on? We need answers.
9. In Android, building an app took me 3 months and I had a lot of work left to do but I got so sick of Android dev I dropped it in favour of Flutter. I built the same app in Flutter and it took me around a month and I completed it all.
If you're a new dev, for the love of all that is good in this world, do NOT get into Android development. Start with Flutter or even iOS. On Flutter and build times are insanely fast and the hot reload is under 500ms constantly. It's a breath of fresh air and will save you a lot of headaches AND it builds for iOS flawlessly.
To the people who build Android, advocate it and work on it, sorry to swear, but fuck you! You have created a mess that we have to work with on a day-to-day basis only for us to get banned from the app store! You have sold us a lie that Android development is amazing with all the sweet treat names and conferences that look bubbly and fun. You have allowed to get it so bad that we can't target an API higher than 18 because some Android users are still using devices that support that!
End this misery. End our pain. End our suffering. Throw this abomination away like you do with some of your other projects and migrate your efforts over to Flutter. Please!
#NoToGoogleIO #AndroidSummitBoycott #FlutterDev #ReactNative16
Just joined devRant! Can't wait to get more involved!
Bored in the lockdown, I built an app which lets you chat with people around you.
Its called Cyrcl!
Built in over ~40 days, I was the sole developer.
Here is the tech stack - React native for the android and ios apps, mongodb and redis for the database, nodejs for the server and aws ec2 for the hosting!
I'd love to get some feedback, or discuss some of the hacks!
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?26
Saw a job posting today for an EXPERT React Native Developer.
At least they didn't ask for years of experience Lol4
Management: ReactNative is great because it is faster!
Me: What else do we get from it?
Management: Facebook made it so it is good!
Choosing ReactNative for my project. Nothing works or compiles. Each fix breaks something. I'll go fishing...5
I wanna start learning mob app development. Which should i choose amongst these and why?
1) React Native
3) ios native app development.
At the end my focus is to earn more from which ever the tech stack i choose.
Worst: Spending a week in npm, node, react hell trying to triage a ReactNative iOS/Android app that even the OG dev couldn't fix and FAILING.
This is the only code in like 20 fuckin years that beat me.
Best: Watching the fall of western democracy with a giant shit eating "I told you so" grin.6
Im planning to switch for a remote company. I have 2 years of internship and 1 year of full time experience.
I also have some GitHub repos where I played around with JS frameworks and I will soon release the beta version of a puzzle game I made with React Naive in my freetime.
Im also planning on creating a simple website for myself on GitHub pages.
Would this be enough for a mid-level fully remote frontend developer position?
Thanks for the answers in advance!10
blank and this shit is happening.
This shit is one of the reason why i don't use things like this.2
I got the core functionality of my Android app working!
But more importantly the dev felt... Fun. The new GUI designer and navigation view/controller is pretty nice.
But also the fact that I'm coding for myself instead of thinking about how to make it sellable...
That and it's easier than getting it to work via ReactNative...
Guess learning React will have to wait... Until it's needed at work.
On another note... My 1 week vacation has come to an end... But lack of motivation and energy prevented me from doing everything I was supposed to do including the other fun stuff...1
Was motivated to do a project with ReactNative for Android but already stuck.
I need to read a SQLite DB file from /data/data/some.other.app/database/DB.db
Yes I am rooted.
1. How does I request root from the App (Android Pie)
2. What SQLite npm package can load from an absolute path. I found a few libs but they don't seem to be full access, just for dbs in the app's own data folder.8
I have a question, let's say I have a website and app both using oAuth facebook login. Should I save the access token provided by facebook in my database and if I should, what will happen to the access token when user logins with facebook on website and then login again with the app? is that mean access token is going to be overwritten by new login? and do you have any other suggestions for 0auth integration?3
Wow..so i decided to try out Swift instead of always writing in ObjC while writing a native module in my React Native project.
I spent a fucking hour trying to figure out how can i write code to get a value from my info.plist in Swift and what i got was a humongous piece of code whereas ObjC does it in one line.
Whats the hype about Swift?!? Its the worst fucking language out there5
A new app called Byte which is Vine remade and exactly same as Vine and the creator of vine made it, my question is what was this app developed in? Flutter, reactnative, native or what?6
I'm curious about which kind of pattern/architecture you are using in your react native apps (big ones).
Wrong place to say this, but I'm asked to work on a React-Native mobile apps, is there a need to mix native code with React, or do I only focus on the part of ReactNative components in the docs?
I do know ReactJs so far what I'm reading is familiar but don't know about mobile apps.
I must give an answer tomorrow morning, and SO will only bring me down if I ask there :)8
BIG QUESTION TIME:
I want to start a small web-dev project. Basically a website with different gigs like a time tracking app. Maybe extend it in the future with other apps.
First I thought of starting with a CMS (I am quite good with Joomla!) but realized it may too soon get to its' limits and personalized extensions are quite a pain with CMS.
So I had this genius idea of working on frontend using ReactNative giving the opportunity to build for mobile in the same time and backend with Python (maybe Django framework).
Here are my questions:
1) Could this be a good solution or combination? (Considering it is more of a fun project)
2) Does anyone know a good tutorial for ReactNative besides the facebook github tutorial?2
Are native Android apps easier to write now than like back in KitKat days?
I need a app that gets root permissions and reads a db file of another app (Yes my phone is rooted).
Anyone can give a gist, I forget do I need to create a Service background worker to do the DB reads... Or just need to send the op to a bg thread with a UI callback sorta like Node...
I did try writing a ReactNative app maybe last year just to try it out but can't seem to easily get root access... And the SQLite package is buggy, couldn't npm install on Win10...14
what's main difference between cross-platform and multi-platform?
and whats main difference between kotlin multiplatform and ReactNative?
i am familiar with both kotlin and NodeJS, What is your suggestion for build a app for ios and android?7
I have an idea for an app and waned to get your opinion on what I should use.
I have experience in Java and ReactJs, but nothing in Swift.
So, I want to know what you all would suggest - should I use React Native or Java and Swift to create both my android and iOS app? I have read mixed reviews concerning React Native and its use longterm? However, it seems like its the easier options to push out both and Android and iOS app.
I'm very unsure, any suggestions would be much appreciated.6
Is it me, or ReactNative just doesn't like working on Windows?
I've tried to get it working a couple of years ago (rn with redux and flux), but without success.
disclaimer: This was before expo (the client) was a thing, and also reactnative itself was really young. Has anyone tried it recently? Any opinions?
Since then I've moved to MacOS, and it worked perfectly (same versions) => not an apple fanboy, so I would like to go back to windows2
I think I may have just had a bit of an epiphany...
Algorithms and Data Structures are sort of like libraries and frameworks.
JS is probably the easiest example since npm has a lot of libraries.
For most cases, underscore.each and lodash.each $.each achieve pretty much the same thing except one maybe better in certain cases.
And data structures are sort of like Angular, React, Electron, ReactNative. Each has its own purpose or style and are good for solving certain types of problems?
So day-to-day you don't really care what Sort() algo you use.. unless you really need to perfoarmance tune it for a specific case.
And data structures, depending on the type of problem you have, one is easier to work/think about the problem in although not examply... Usually have to use a few of them at once.
How is this going to help me in interviews... I'm not sure... other than reconfirming that knowing specific implementations of Sort and Trees is usually BS... most of the time just need to know you should Sort or use a Tree...
I’m learning react native frontend so can anyone please post random design specs links? I promise to show result, push code to GitHub and maybe a YouTube video of me doing the design.
Note: I’ll be designing a single page per design1
Ok, i will give a try to crossplateform mobile dev.
So what's ur advice fellow programers ? Xamarin or ReactNative ?
1 choice, 1 argument (main one)11
Anyone want to do a ReactNative project with me? I'm trying to learn and would would to work with someone who wants to learn it too.1
Who else finds HTML/CSS to be just plain bad?
since that's what the web adopted, apparently no matter what you are developing if it involves a GUI then the design method almost always follows in the same path as the web.
that's not the issue though, the real problem is that the web adopted a very horrible way to create a UI, while HTML might have been fine for 90s-style websites I just feel like its a very lousy way to create a modern interactive webapp UI, its just very painfully obvious that it wasn't designed for that purpose. remind me again what HTML stands for? "HyperText Markup Language" yea that sounds about right. and CSS really doesn't help but double down on the flaws of HTML.
on a whim I can come up with a better method:
this makes a lot more sense than the footer/body design or the obviously duck-taped attempts at controlling the style in CSS, like flow, and absolute-position.
am I alone in this?10
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.
It feels weird after seeing that the most frustrated cross-platform framework has such a big ecosystem:
Anyways, I need to hook myself up with flutter as I see it as a better alternative to React Native.
The article mainly summarised as follows :
- react is a very lean library but does not provide a lot of features out of the box.
- angular is a very powerful framework which works with typescript and provides a lot of functionalities like routes(?), pwas(?) from within .
- vue is a kind of mix which tries to provide as much features as angular, but uses plain js
From those descriptions, i felt like angular is the best and the worst for me at the same time.
I appreaciated detailed, multi functional environments like that of java language and Android OS because google provides strong support and ensures the apis work while enforcing the best practices through their architectures (Like MVVM. I am currently a college student and i don't think i would have ever implemented a scalable app before joining a company, if i was not exposed to a practise like mvvm)
But at the same time it is taking out all the self learning part by providing a complete environment and making us kind of just 3rd party users trying to fix 2 wires provided by them.
I mean google itself might not hire a dev who just worked on angular their whole life, right? They know that the guy knows only the stuff *they* provided to him, nothing more. I bet they would themselves want a react person who came with his own implementation of single page app without depending on a framework.
What do you guys think? Am I passing the judgement too soon? I don't know much of these big stuff, just saw that article and related it to my past experience.
Do you prefer react/reactnative for your webapps or angular /vue ?and what the hell is rxJS?5
Been stuck in this step for a while now, tried all solutions from StackOverflow.
This community is my only hope now...
React native: Is a bare workflow better or Expo for my first time building with it? I've already gone with expo quite a bit of the ways and im finding that I have to use expo's libraries (location, permissions, ext) if i want my life to be made easy. Cause i cant use react-native cli to link libraries automatically or open them in xcode to link manually sense they're not technically xcode apps.
Is that the only answer with expo is to just use all the expo libraries in effort to stay compatible and not handle more overhead ?4