Podcasts about react native web

Another episode of "We React to News" is upon us! Today, Mazen and Robin are talking about all sorts of juicy topics like Expo 47, Solito, and Meta adopting Kotlin as primary language for Android development, just to name a few. This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Helpful Links:Expo SDK 47 beta is now available | by Brent Vatne | Oct, 2022 | ExpositionIntroduction | Expo RouterExpo Router | SolitoRFC: File System-Based Native Routing with Expo and React Native | by Evan Bacon | Sep, 2022RNR 224 - React Native Web on Next.js with Fernando RojoFrom zero to 10 million lines of Kotlin - Engineering at MetaCreate React Native Library 0.25Alexandre Moureaux New Architecture Benchmarking on TwitterReact Native types moving out of DefinitelyTypedhttps://twitter.com/kelset/status/1572994139649720322https://github.com/react-native-community/discussions-and-proposals/discussions/490#discussioncomment-3693520Connect With Us!React Native Radio - @ReactNativeRdioMazen - @mazenchamiRobin - @robin_heinze

Jamon, Robin, and Mazen talk with former RNR host, Josh Justice, about building an Expo App for Mobile and Web. There is also some spirited conversation about skiing. This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Helpful Links:Josh's talk at ReactATLSurelySurely Github sourceReact Native WebReact Native Testing LibraryReact Navigation for WebConnect With Us!React Native Radio - @ReactNativeRdioJosh -  codingitwrong.comMazen - @mazenchamiRobin -  @robin_heinze

In this episode, Mazen and Jon Major are joined by Fernando Rojo, Co-Founder and CTO at BeatGig, to discuss the ins and outs of working with React Native Web on Next.js.This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Helpful Links:PATOSBeatGigFernando's next.js Conf 2021  talk about React Native  + Next.jsResourceshttps://github.com/pmndrs/zustandhttps://github.com/nandorojo/motihttps://github.com/nandorojo/dripsyConnect With Us!React Native Radio - @ReactNativeRdioFernando - @FernandoTheRojoJon Major -  @jonmajorcMazen - @mazenchami

This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Helpful Links:https://github.com/necolas/react-native-web/blob/master/packages/docs/src/guides/accessibility.stories.mdxReact Native Router Flux: https://github.com/aksonov/react-native-router-fluxReact Native Web: https://github.com/necolas/react-native-webHarmonyOS: https://en.wikipedia.org/wiki/Harmony_OSConnect With Us! Harris - @nomadicspoonJamon - @jamonholmgrenRobin - @robin_heinzeSimon - @sstur_

Will Candillon is back and he brought the one thing this podcast is missing: a topic. Will and I talk about how we got into programming, reminisce about Macromedia Dreamweaver and Texas Instruments' classic TI-82 calculator, profess our love for React Native, and Will also gives me a quick breakdown of React Native Web, all in exactly 10 minutes. Follow Will on Twitter @wcandillon Watch him on YouTube https://www.youtube.com/user/wcandill Triple T on Twitter @tripletpodcast1 John on Twitter @johnhaupenthal

Graham Conzett has been a developer for 12 years. He has worked with Ruby and Rails for half of that, and currently works for a company that does large format touchscreens. Graham gave a talk at RailsConf 2018 called “Old School JavaScript and Rails” where he talks about the experience of JavaScript fatigue. The world of JavaScript changes very quickly, and sometimes it feels like there’s a new framework every week. Because there is no clear winner among these frameworks, many Rails developers feel compelled to reach for something like React. However, there are many strategies for doing JavaScript in Ruby and in Rails that existed before these frameworks, so you can accomplish what you want to get done without bringing one in. Remember that all of them can coexist side by side, so you don’t have to pick one strategy. The panel discusses the effect that adopting a new technology can have on the team, such as the learning curve and hiring people that specialize in it.  To illustrate this, Graham talks about the company he works for. Their app is a 90% is a Rails app, and one component has a lot of React. He talks about how they came up with that strategy and how they have kept React isolated to that page. It’s crept into some other little places, but there is a document in the team charter that defines where and why they use certain things, and that has kept it limited. Graham talks about the tradeoffs between choosing to stay in Rails or introduce React. If you bring in React, you have to bring in a different testing framework. React also has a bigger learning curve than standard HTML or CSS. There are far less conventions around React than Rails, so you have to spend time coming to a consensus as a team. Webpacker helps with this to a degree, but it also pulls in a bunch of third party plugins, so Rails is no longer writing the rules and you may have to debug random plugins. If you want to avoid adding a framework like React, consider using ujs, or Unobtrusive JavaScript. These are JavaScript ‘helpers’ included in the Rails bundle that you can add to various buttons that help you decorate and enhance. You don’t have to change much of your HTML frontend code but it makes it more interactive. Graham talks about he uses them and why he likes them. The panel compares using ujs to other strategies like using Stimulus or ‘sprinkles’ of JavaScript. For small JS sprinkles, Graham advises to keep that focused on a single HTML element and bound to a single event handler. Ujs works best when you piggyback off of that Rails/Rest related stuff, and Stimulus is more about manipulating parts on the page that don’t have a need for asynchronous request. You can really use ujs everywhere, so the three techniques are not mutually exclusive. Graham gives advice to developers considering pulling in a frontend framework. He says to start with minimal JS and then talk to your team about when it feels right to do it, because that’s a tricky conversation to know what your expectations are and problems you’re trying to solve. Sometimes things will force the issue and make you want to explore using frontend frameworks. When it’s a time saver, it makes your team scale better, or when you have something you just can’t do without it, then that might be the right time to use React. The show concludes with the panel discussing their experiences with different compiling languages like TypeScript. They talk about what influences the tools people choose. They agree that the most important thing is getting working code out there, it doesn’t really matter how it’s written, but to only pull things in when you know you need it. Panelists Charles Max Wood Andrew Mason David Kimura Nate Hopkins With special guest: Graham Conzett Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Adventures in Angular Links Old School JavaScript and Rails at RailsConf 2018 React React Native React Native Web Jest Capybara Webpacker Rails-ujs Turbolinks Stimulus Stimulus Reflex Babel TypeScript Actionview components Angular Follow DevChatTV on Facebook and Twitter Picks Charles Max Wood: St. George Marathon OBS David Kimura: WeDo 2.0 by Lego Workflow Automation Self Hosted Andrew Mason: Publish to Github action JustDunning.com Nate Hopkins: Company of One by Paul Jarvis IndieHackers Graham Conzett: Basecamp’s Shape Up Pigeonforteachers.com  IKE Smart City Follow Graham @gconzett on Twitter and Github

Graham Conzett has been a developer for 12 years. He has worked with Ruby and Rails for half of that, and currently works for a company that does large format touchscreens. Graham gave a talk at RailsConf 2018 called “Old School JavaScript and Rails” where he talks about the experience of JavaScript fatigue. The world of JavaScript changes very quickly, and sometimes it feels like there’s a new framework every week. Because there is no clear winner among these frameworks, many Rails developers feel compelled to reach for something like React. However, there are many strategies for doing JavaScript in Ruby and in Rails that existed before these frameworks, so you can accomplish what you want to get done without bringing one in. Remember that all of them can coexist side by side, so you don’t have to pick one strategy. The panel discusses the effect that adopting a new technology can have on the team, such as the learning curve and hiring people that specialize in it.  To illustrate this, Graham talks about the company he works for. Their app is a 90% is a Rails app, and one component has a lot of React. He talks about how they came up with that strategy and how they have kept React isolated to that page. It’s crept into some other little places, but there is a document in the team charter that defines where and why they use certain things, and that has kept it limited. Graham talks about the tradeoffs between choosing to stay in Rails or introduce React. If you bring in React, you have to bring in a different testing framework. React also has a bigger learning curve than standard HTML or CSS. There are far less conventions around React than Rails, so you have to spend time coming to a consensus as a team. Webpacker helps with this to a degree, but it also pulls in a bunch of third party plugins, so Rails is no longer writing the rules and you may have to debug random plugins. If you want to avoid adding a framework like React, consider using ujs, or Unobtrusive JavaScript. These are JavaScript ‘helpers’ included in the Rails bundle that you can add to various buttons that help you decorate and enhance. You don’t have to change much of your HTML frontend code but it makes it more interactive. Graham talks about he uses them and why he likes them. The panel compares using ujs to other strategies like using Stimulus or ‘sprinkles’ of JavaScript. For small JS sprinkles, Graham advises to keep that focused on a single HTML element and bound to a single event handler. Ujs works best when you piggyback off of that Rails/Rest related stuff, and Stimulus is more about manipulating parts on the page that don’t have a need for asynchronous request. You can really use ujs everywhere, so the three techniques are not mutually exclusive. Graham gives advice to developers considering pulling in a frontend framework. He says to start with minimal JS and then talk to your team about when it feels right to do it, because that’s a tricky conversation to know what your expectations are and problems you’re trying to solve. Sometimes things will force the issue and make you want to explore using frontend frameworks. When it’s a time saver, it makes your team scale better, or when you have something you just can’t do without it, then that might be the right time to use React. The show concludes with the panel discussing their experiences with different compiling languages like TypeScript. They talk about what influences the tools people choose. They agree that the most important thing is getting working code out there, it doesn’t really matter how it’s written, but to only pull things in when you know you need it. Panelists Charles Max Wood Andrew Mason David Kimura Nate Hopkins With special guest: Graham Conzett Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Adventures in Angular Links Old School JavaScript and Rails at RailsConf 2018 React React Native React Native Web Jest Capybara Webpacker Rails-ujs Turbolinks Stimulus Stimulus Reflex Babel TypeScript Actionview components Angular Follow DevChatTV on Facebook and Twitter Picks Charles Max Wood: St. George Marathon OBS David Kimura: WeDo 2.0 by Lego Workflow Automation Self Hosted Andrew Mason: Publish to Github action JustDunning.com Nate Hopkins: Company of One by Paul Jarvis IndieHackers Graham Conzett: Basecamp’s Shape Up Pigeonforteachers.com  IKE Smart City Follow Graham @gconzett on Twitter and Github

Graham Conzett has been a developer for 12 years. He has worked with Ruby and Rails for half of that, and currently works for a company that does large format touchscreens. Graham gave a talk at RailsConf 2018 called “Old School JavaScript and Rails” where he talks about the experience of JavaScript fatigue. The world of JavaScript changes very quickly, and sometimes it feels like there’s a new framework every week. Because there is no clear winner among these frameworks, many Rails developers feel compelled to reach for something like React. However, there are many strategies for doing JavaScript in Ruby and in Rails that existed before these frameworks, so you can accomplish what you want to get done without bringing one in. Remember that all of them can coexist side by side, so you don’t have to pick one strategy. The panel discusses the effect that adopting a new technology can have on the team, such as the learning curve and hiring people that specialize in it.  To illustrate this, Graham talks about the company he works for. Their app is a 90% is a Rails app, and one component has a lot of React. He talks about how they came up with that strategy and how they have kept React isolated to that page. It’s crept into some other little places, but there is a document in the team charter that defines where and why they use certain things, and that has kept it limited. Graham talks about the tradeoffs between choosing to stay in Rails or introduce React. If you bring in React, you have to bring in a different testing framework. React also has a bigger learning curve than standard HTML or CSS. There are far less conventions around React than Rails, so you have to spend time coming to a consensus as a team. Webpacker helps with this to a degree, but it also pulls in a bunch of third party plugins, so Rails is no longer writing the rules and you may have to debug random plugins. If you want to avoid adding a framework like React, consider using ujs, or Unobtrusive JavaScript. These are JavaScript ‘helpers’ included in the Rails bundle that you can add to various buttons that help you decorate and enhance. You don’t have to change much of your HTML frontend code but it makes it more interactive. Graham talks about he uses them and why he likes them. The panel compares using ujs to other strategies like using Stimulus or ‘sprinkles’ of JavaScript. For small JS sprinkles, Graham advises to keep that focused on a single HTML element and bound to a single event handler. Ujs works best when you piggyback off of that Rails/Rest related stuff, and Stimulus is more about manipulating parts on the page that don’t have a need for asynchronous request. You can really use ujs everywhere, so the three techniques are not mutually exclusive. Graham gives advice to developers considering pulling in a frontend framework. He says to start with minimal JS and then talk to your team about when it feels right to do it, because that’s a tricky conversation to know what your expectations are and problems you’re trying to solve. Sometimes things will force the issue and make you want to explore using frontend frameworks. When it’s a time saver, it makes your team scale better, or when you have something you just can’t do without it, then that might be the right time to use React. The show concludes with the panel discussing their experiences with different compiling languages like TypeScript. They talk about what influences the tools people choose. They agree that the most important thing is getting working code out there, it doesn’t really matter how it’s written, but to only pull things in when you know you need it. Panelists Charles Max Wood Andrew Mason David Kimura Nate Hopkins With special guest: Graham Conzett Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Adventures in Angular Links Old School JavaScript and Rails at RailsConf 2018 React React Native React Native Web Jest Capybara Webpacker Rails-ujs Turbolinks Stimulus Stimulus Reflex Babel TypeScript Actionview components Angular Follow DevChatTV on Facebook and Twitter Picks Charles Max Wood: St. George Marathon OBS David Kimura: WeDo 2.0 by Lego Workflow Automation Self Hosted Andrew Mason: Publish to Github action JustDunning.com Nate Hopkins: Company of One by Paul Jarvis IndieHackers Graham Conzett: Basecamp’s Shape Up Pigeonforteachers.com  IKE Smart City Follow Graham @gconzett on Twitter and Github

Sponsors Infinite Red Adventures in DevOps G2i CacheFly Panel Peter Piekarczyk Don Bora Rob Volk Summary Don Bora, a Native developer, is being pushed by his company to cross-platform with React Native, he joins the podcast to ask the panel for advice. The panel begins by discussing the amount of code reuse. Rob and Peter explain the importance of using expo and how it can solve most problems. They share resources for Don to get started. The panel compares React Native and Native; what types of apps should be built with each. The considerations that should be made and the cost associated with cross platforming is discussed. The panel discusses Reason, React Native Web and Expo Web. Links https://github.com/react-native-community/lottie-react-native https://www.npmjs.com/package/react-native-reanimated https://yogalayout.com/ https://reasonml.github.io/ https://github.com/necolas/react-native-web https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Don Bora: When a Colleague is Grieving Rob Volt: Expo Unit Modules Peter Piekarcyzk: Hermes

Sponsors Infinite Red Adventures in DevOps G2i CacheFly Panel Peter Piekarczyk Don Bora Rob Volk Summary Don Bora, a Native developer, is being pushed by his company to cross-platform with React Native, he joins the podcast to ask the panel for advice. The panel begins by discussing the amount of code reuse. Rob and Peter explain the importance of using expo and how it can solve most problems. They share resources for Don to get started. The panel compares React Native and Native; what types of apps should be built with each. The considerations that should be made and the cost associated with cross platforming is discussed. The panel discusses Reason, React Native Web and Expo Web. Links https://github.com/react-native-community/lottie-react-native https://www.npmjs.com/package/react-native-reanimated https://yogalayout.com/ https://reasonml.github.io/ https://github.com/necolas/react-native-web https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Don Bora: When a Colleague is Grieving Rob Volt: Expo Unit Modules Peter Piekarcyzk: Hermes

Evan Bacon is a Software Engineer at Expo.io. Prior to that, Evan was a designer at Frog Design and Master Builder at LEGO. He joins hosts Jared Palmer and Ken Wheeler on the Undefined to talk about React Native, game development, and his unique origin story. The gang also discusses $900k developer salaries, moving to NYC, and White Claw.Evan Bacon - Twitter, GithubKen Wheeler – Twitter, GitHub, WebsiteJared Palmer – Twitter, GitHub, WebsiteG2i - SponsorIf you're building a new product, G2i is a company that can help you find a developer who can build the first version. G2i is a hiring platform run by engineers that matches you with React, React Native, GraphQL, and mobile engineers who you can trust. Whether you are a new company building your first product or an established company that wants additional engineering help, G2i has the talent you need to accomplish your goals. Go to g2i.co to learn more about what G2i has to offer.

Sponsors Radio Infinite Red TripleByte offers a $1000 signing bonus CacheFly Panel Charles Max Wood Joined by Special Guest: Anna Doubkovar Summary Anna Doubkovar, a developer at Hive, shares her experience switching to React Native from React. Anna and Charles Max Wood discuss the reusability when moving from React to React Native. Anna talks about using React Native Web. Charles asks Anna about performance, how they measure performance and what kinds of performance changes they are making to their apps. Anna shares how helpful users are in discovering performance problems in mobile apps. Anna and Charles discuss the benefits of working with React Native and give tips for those getting started in React Native.  Links https://github.com/react-navigation/react-navigation https://twitter.com/lithinn https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Charles Max Wood: Soccer Kingdoms of Heckfire Devchat.tv Youtube Channel https://75hard.com/info Anna Doubkovar: On Becoming a Person: A Therapist's View of Psychotherapy

Sponsors Radio Infinite Red TripleByte offers a $1000 signing bonus CacheFly Panel Charles Max Wood Joined by Special Guest: Anna Doubkovar Summary Anna Doubkovar, a developer at Hive, shares her experience switching to React Native from React. Anna and Charles Max Wood discuss the reusability when moving from React to React Native. Anna talks about using React Native Web. Charles asks Anna about performance, how they measure performance and what kinds of performance changes they are making to their apps. Anna shares how helpful users are in discovering performance problems in mobile apps. Anna and Charles discuss the benefits of working with React Native and give tips for those getting started in React Native.  Links https://github.com/react-navigation/react-navigation https://twitter.com/lithinn https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio Picks Charles Max Wood: Soccer Kingdoms of Heckfire Devchat.tv Youtube Channel https://75hard.com/info Anna Doubkovar: On Becoming a Person: A Therapist's View of Psychotherapy

Sponsors Netlify Sentry use the code “devchat” for 2 months free on Sentry’s small plan Triplebyte offers a $1000 signing bonus CacheFly Panel Nader Dabit Lucas Reis Thomas Aylott Episode Summary Today the panel is discussing the necessity of companies having a dedicated frontend team. They begin by discussing the technologies that might be used by a dedicated frontend team. According to the panel, the necessity of a frontend team is determined by the size of the company. When you try to have a frontend team too soon, it ends up being a huge debacle, but once you get bigger and have multiple teams, it gets more useful. A company is ready for a dedicated frontend team when it is able to build with a common set of components. The panel discusses the concept of ownership in a company. Nader believes that things should be run where there is a team that’s in charge of building a component, and once the component has shipped, they are no longer in charge. The other panelists disagree with that method because they believe there is a danger of the project getting bloated. Thomas shares his experience with working for Facebook and Lucas talks about how he has previously set up his teams. They talk about the necessity of having a design system before having a React design system, and they all agree that it is useful Nader shares his experience with his brother working for Cartoon network and the design rules they had for the websites for each show like Dexter’s Lab and PowerPuff Girls. Since the panel agrees on the importance of consistency in visual communication and designs, they delve into deciding what is owned by the design system and what is shared between other teams, who maintains these things, and how to differentiate between the different kinds of components. They talk about the idea of Atomic Design in programming, separating component into categories called names like atoms, molecules, organisms, etc. Nader talks about his experience with this method. He found it difficult because components didn’t always fit cleanly into one category. The panel believes that it all comes back to ownership and it is important that companies are handling ownership well Links Storybook Frontend Cloudera Next.js Gatsby React Native Web Docz Material Follow DevChat on Facebook and Twitter Picks Nader Dabit: React Native in Action by Nader Dabit Lucas Reis: Kickstarting a Library of Internal React Components for Multiple Teams by Javier Lefevre Thomas Aylott: The E-Myth Revisited The Design of Everyday Things Atomic Design by Brad Frost

Sponsors Netlify Sentry use the code “devchat” for 2 months free on Sentry’s small plan Triplebyte offers a $1000 signing bonus CacheFly Panel Nader Dabit Lucas Reis Thomas Aylott Episode Summary Today the panel is discussing the necessity of companies having a dedicated frontend team. They begin by discussing the technologies that might be used by a dedicated frontend team. According to the panel, the necessity of a frontend team is determined by the size of the company. When you try to have a frontend team too soon, it ends up being a huge debacle, but once you get bigger and have multiple teams, it gets more useful. A company is ready for a dedicated frontend team when it is able to build with a common set of components. The panel discusses the concept of ownership in a company. Nader believes that things should be run where there is a team that’s in charge of building a component, and once the component has shipped, they are no longer in charge. The other panelists disagree with that method because they believe there is a danger of the project getting bloated. Thomas shares his experience with working for Facebook and Lucas talks about how he has previously set up his teams. They talk about the necessity of having a design system before having a React design system, and they all agree that it is useful Nader shares his experience with his brother working for Cartoon network and the design rules they had for the websites for each show like Dexter’s Lab and PowerPuff Girls. Since the panel agrees on the importance of consistency in visual communication and designs, they delve into deciding what is owned by the design system and what is shared between other teams, who maintains these things, and how to differentiate between the different kinds of components. They talk about the idea of Atomic Design in programming, separating component into categories called names like atoms, molecules, organisms, etc. Nader talks about his experience with this method. He found it difficult because components didn’t always fit cleanly into one category. The panel believes that it all comes back to ownership and it is important that companies are handling ownership well Links Storybook Frontend Cloudera Next.js Gatsby React Native Web Docz Material Follow DevChat on Facebook and Twitter Picks Nader Dabit: React Native in Action by Nader Dabit Lucas Reis: Kickstarting a Library of Internal React Components for Multiple Teams by Javier Lefevre Thomas Aylott: The E-Myth Revisited The Design of Everyday Things Atomic Design by Brad Frost

Brent Vatne is a Software Engineer at Expo. He joins hosts Jared Palmer and Ken Wheeler on The Undefined to talk about the future of the web, native development, and more.FeaturingBrent Vatne - Twitter, GithubKen Wheeler – Twitter, GitHub, WebsiteJared Palmer – Twitter, GitHub, Website

Un épisode avec : - Maxime (https://twitter.com/MoOx) - Mathieu (https://twitter.com/Zoontek) - Georges (https://twitter.com/jojmaht) - Matthias (https://twitter.com/bloodyowl) Les liens: - Le nouveau site: https://putaindecode.io - Comment on l'a fait: https://putaindecode.io/articles/comment-on-a-fait-ce-site - Les sources: https://github.com/putaindecode/putaindecode.io - ReactDOMServer: https://reactjs.org/docs/react-dom-server.html - Emotion: https://emotion.sh/docs/introduction - React Native Web: https://github.com/necolas/react-native-web - Prerender.io : https://prerender.io

Amanda joins Derek to discuss KotlinConf, powerful IDEs, our Ralphapalooza hackathon, and the React Native experience from a native mobile developer's perspective. A View State Machine for Network Calls on Android - Amanda's KotlinConf talk How to Build a React App in Kotlin by Dave Ford Kotlin Static Analysis with Android Lint by Tor Norbye ReSharper: Visual Studio Extension for .NET Developers thoughtbot Trail Maps Lucky - a web framework for Crystal Frinkiac thoughtbot does screen printing The Pixar Theory MLB Twitter thinks something fishy is going on with Jeter trading Stanton to Yankees - CBSSports.com React Native Web

On this episode Alex and David talk about finding work, doing the work, invoicing for the work and hopefully getting paid on time for the work. # Follow Us Alex - twitter.com/alexbilbie David - twitter.com/davzie # Give Us Feedback or Ask Questions feedback@codingsolo.works twitter.com/coding_solo # Alex's audio setup http://imgur.com/a/6wbzd # Show Links YunoJuno - https://www.yunojuno.com/ldn/ Dice Jobs - http://uk.dice.com/ CW Jobs - https://www.cwjobs.co.uk/ Alex’s OAuth 2.0 server library - https://github.com/thephpleague/oauth2-server Double Your Freelance Rate - https://doubleyourfreelancing.com/ Flat rate VAT - https://www.gov.uk/vat-flat-rate-scheme Standard rate VAT - https://www.gov.uk/vat-registration React Native - https://facebook.github.io/react-native/ Apache Cordova - https://cordova.apache.org/ React Native Web - https://github.com/necolas/react-native-web UK Freelance Rate Calculator (seems accurate for London at least) - http://ournameismud.co.uk/fraq/ # Crunch Accountants Crunch puts freelancers, contractors and small businesses in control of their finances with expert accredited accountants and beautifully simple online software. http://www.crunch.co.uk/?aid=codingsolo Please tell them the Coding Solo podcast sent you!

Derek chats with Ian Anderson about developing a mobile app for iOS and Android with React Native. Ian on Twitter Purple (T)Rain GenServer Agent React Native Flow Elm Native UI React Native Web