3 ms·

What languages did you write it in? What stack did you use for your backend? What format is video stored in? What format is it played back in (ie, real video or

What languages did you write it in? What stack did you use for your backend? What format is video stored in? What format is it played back in (ie, real video or chopped up video like HTS/DASH)? Can I users get access to direct video file links? How much does bandwidth cost you? Did you chose to use an existing CDN or roll your own? Is this only for Apple (tm) smart phones? Is it only for smart phones? How do you intend to make money?

eorge_g 8y ago
Great questions! We learned a ton doing the video work on this never having worked with video encoding before. We built front end using React Native (ejected from Expo), backend API using Rails (as that's our most comfortable stack). The video encoding processing is handled by Amazon Elastic Transcoder, hosting the videos on s3. There's a sneaky amount of transcoding involved in the simple app, but it's all cheap at a few dollars a month so far with some use. We're not using a CDN atm but are looking at using cloudfront. Right now it's only on Apple phones, but since we build the front end in React Native building for Android is on the roadmap if there's customer demand!
- winsome 8y ago
  Why did you choose to use React Native if you weren't planning to use it for cross-platform purposes out of the box? Why not use swift or objective-c and then port to Android if there's customer demand?
  - sbfriends 8y ago
    > Why did you choose to use React Native if you weren't planning to use it for cross-platform purposes out of the box? Why not use swift or objective-c and then port to Android if there's customer demand? There's lots of reasons someone might want to start with Expo while developing an app. If their team doesn't have native experience, it's far more accessible than needing to maintain a native stack (or two should they support Android). It also supports the ability for OTAs out of the box, which allows them to be responsive to feedback / bugs / feature requests. There's more to RN/Expo than "do you plan on releasing a cross-platform product at once". Even if their road map is "Apple now, Android later" the decision would still be justified.

eorge_g 8y ago

Great questions! We learned a ton doing the video work on this never having worked with video encoding before. We built front end using React Native (ejected from Expo), backend API using Rails (as that's our most comfortable stack). The video encoding processing is handled by Amazon Elastic Transcoder, hosting the videos on s3. There's a sneaky amount of transcoding involved in the simple app, but it's all cheap at a few dollars a month so far with some use. We're not using a CDN atm but are looking at using cloudfront. Right now it's only on Apple phones, but since we build the front end in React Native building for Android is on the roadmap if there's customer demand!

winsome 8y ago
Why did you choose to use React Native if you weren't planning to use it for cross-platform purposes out of the box? Why not use swift or objective-c and then port to Android if there's customer demand?
- sbfriends 8y ago
  > Why did you choose to use React Native if you weren't planning to use it for cross-platform purposes out of the box? Why not use swift or objective-c and then port to Android if there's customer demand? There's lots of reasons someone might want to start with Expo while developing an app. If their team doesn't have native experience, it's far more accessible than needing to maintain a native stack (or two should they support Android). It also supports the ability for OTAs out of the box, which allows them to be responsive to feedback / bugs / feature requests. There's more to RN/Expo than "do you plan on releasing a cross-platform product at once". Even if their road map is "Apple now, Android later" the decision would still be justified.