サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
Switch 2
shift.infinite.red
Artwork by Jenna FucciFlutter and React Native are natural competitors as two of the most used multi-platform mobile app frameworks. Debates swirl…developers argue…and, in the end, apps are shipped, using one or the other. So which is better? The smart answer, the one that senior engineers will say with a cheeky grin, is: “It depends. Both have pros and cons, and in the end it’s a decision about t
I turned to Twitter to see what I should write about next, and after over a hundred votes, the winner was to finish this blog post! Twitter Driven Blogging — Let’s GO!So you’ve finished your React Native app, and you’re ready to ship it out the door. What’re your final steps? No, we’re not going to cover silly answers like “make sure your tests pass”, or “time to add smoke tests” (what does that e
At Infinite Red, we’ve been using Yarn for several years now — virtually since it was released. We even released an NPM vs Yarn cheat sheet that has been downloaded thousands of times! Recently, Yarn 2 was announced, with PNP (plug ’n’ play) support, constraints, and many other improvements. The announcement brought about some controversy in the community due to how some of the technical decisions
RESTful API Versioning, though a simple and elegant concept, is a LOT harder to enforce than it sounds. It’s hard to not break backward compatibility on a continually evolving API, and though API versioning is a great concept, it’s rarely followed without flaw. There’s a reason why throngs are flocking toward intermediaries like GraphQL. RESTful API idealism crashes apps. You know it. Have you toi
PLEASE NOTE: This was written in react-navigation 1.x. Things have changed and I will need to updated the blog post for 2.x I’m sure you’ve read the docs on the react-navigation drawer, thus why you’re here. Navigation sounds simple, but it never is. React Native has a short yet sordid history with navigation. Personally, I’ve had to solve the drawer problem three times over the past two years. Al
We recently finished up a large Phoenix project at Infinite Red, and we learned some tips and tricks along the way that I want to share. Overall, we’ve been impressed at how well organized and maintainable a Phoenix project can be beyond 10,000 lines of code. Some of the tips in this post are specific to Phoenix, others could be equally applied to Rails or other web frameworks. None of them are me
Okay, so you’ve heard about this new JavaScript package manager called yarn, installed it with npm i -g yarn, and now you want to know how to use it? For the most part if you know NPM, you’re already set! Here are the key notes for switching. 👍 Feel free to bookmark this article, as it will update often as yarn grows. Cheat Sheet — What you need to knownpm install === yarn Install is the default
I recently started working on a Phoenix project at Infinite Red that uses Elasticsearch to power a search feature. In our development environments, we needed a good way to ensure that Elasticsearch was running whenever Phoenix was running. Obviously, there are a lot of ways we could do this. We could, for example, have everyone install Elasticsearch through Homebrew with “brew install elasticsearc
react-native - A framework for building native apps with React. Whether you’re experienced in mobile apps or not, you don’t have to spend much time before you end up putting something behind the keyboard. Just look at that form, hidden away and inaccessible under that keyboard! It’s such an annoying problem, and devs have to solve it often. I used to use a pod to help avoid this, but pods require
Some of the most fragile, embarrassing, and unreadable code you will write is flow control. — Beowulf So What’s the Problem Here Anyway?Look. You know how it goes. Just call an API and grab the data. Simple right? No worries! Promise!Oh, but it might timeout after 30 seconds. So trap for that. And we should also handle server errors because the backend team is using PHP (zing!). Then once we get t
You’re sold on React Native, but how much do you need to learn to build a “normal” app? This 3-part guided tour will help with that answer. Congratulations!You were cautious. You weighed the pros and cons. You’re ready to get started. Now what? ¯\_(ツ)_/¯ How hard is it to actually build something? How much do I need to learn? The goal of this 3-part article is to answer those questions. To survey
Rails 5.0 is approaching, bringing with it niceties for websockets, backend-only API servers, and revamping the command layer. Version 4.0 brought turbolinks, russian-doll caching, the queue API, and a host of improvements. All of these, except maybe turbolinks, were great new features but did not fundamentally alter the way applications are built in Rails. That’s good news! It means Rails is a ma
Yes, yes I am.I really do enjoy React Native, as my previous article states. There’s a lot of reasons to use it, but just because I advocate RN, doesn’t mean some things don’t suck. Just like any relationship, you have to be in it to really understand. Trust me, it’s not all rainbows and unicorns. Here’s what hurts: React LimboMost of the time, I hit run in Xcode and I instantly minimize it. I’m u
このページを最初にブックマークしてみませんか?
『shift.infinite.red』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く