Experimenting with React Native & Expo’s Audio API

  • This year, we’re working on a complete refresh (Winds 2.0) that will introduce podcast support, enhanced social functionality, native iOS and Android applications, and much more.
  • With that, we have decided to use React Native to support our iOS and Android builds – a framework that will allow our development team to write applications that target multiple operating systems, with pure JavaScript.
  • We decided to build an audio player for iOS and Android with Expo’s powerful audio API and, of course, React Native.
  • Without React Native and the help of Expo, we would not have been able to target multiple operating systems in the timeframe that we have allotted and we would have to work with two separate codebases.
  • By experimenting and building a fully functional proof of concept, we’re now one step closer to Winds 2.0, and couldn’t be happier to announce that the code is 100% open-source on GitHub.

Stream is hiring Go, Python, and Machine Learning Engineers. Join our team and help powers the feeds for more than 200 million end users!
Continue reading “Experimenting with React Native & Expo’s Audio API”

BTS: #GraphQLRadio – GraphQL Weekly – Medium

Introducing #GraphQLRadio  #apollostack #graphql #react #javascript #reactjs

  • BTS: #GraphQLRadioI am extremely excited to announce that today we are publicly releasing our new podcast, GraphQL Radio!It’s been a great experience ideating the direction of this show, so I just want to give you all a little behind the scenes look at how we got here!Before we begin…What is GraphQL Radio?GraphQL Radio aims to fill a gap in the GraphQL community by providing really informational content from notable library authors, companies, and core contributors.
  • Our main goal was to help give valuable information from the most novice GraphQL user to the most seasoned vets.Having experience with podcasts, and listening to so many, we knew that we wanted the format of the show to be simple: a technical conversation.
  • You can imagine conversations can lead to code samples, which ultimately provides an amazing content experience for everyone watching!Who are we?It all started with this tweet:Immediately Johannes Schickling, the CEO of Graphcool, reached out to me and had told me that Graphcool was interested in making a podcast as well.
  • Correct it for the next show.Digestable ContentLastly we wanted to provide a website for people to come view the show and all its available formats:You can view all our episodes here: www.graphqlradio.comWhat’s up next?Well first, I encourage you to checkout our episode with Danielle Man.
  • It was such an amazing conversation with a fellow engineer, I’m really happy with how it turned out.You can view that episode here.This next week we have a really nice treat for everyone, and something surely will make this show even more exciting.

I am extremely excited to announce that today we are publicly releasing our new podcast, GraphQL Radio! It’s been a great experience ideating the direction of this show, so I just want to give you…
Continue reading “BTS: #GraphQLRadio – GraphQL Weekly – Medium”

Index Signatures · TypeScript Deep Dive

  • interface Foo { [key: string ]: number x: number ; } let foo: Foo = {x: 1 ,y: 2 }; // Directly foo[ x ]; // number // Indirectly let x = x foo[x]; // number
  • let obj = { toString(){ return Hello } } let foo: any = {}; // ERROR: the index signature must be string, number …
  • TypeScript index signatures must be either string or number
  • As soon as you have a string index signature, all explicit members must also conform to that index signature.
  • E.g. say you want to make sure than anything that is stored in an object using a string conforms to the structure {message: string} .

An Object in JavaScript (and hence TypeScript) can be accessed with a string to hold a reference to any other JavaScript object.
Continue reading “Index Signatures · TypeScript Deep Dive”