Neat idea. Anything to share about how you launched this? Is it on Shopify or another ecommerce engine?
I've heard that Instagram oauth access can be difficult to get approved for production use, were they giving you a tough time when you went through the approval process.
Thanks. Answering your questions this is a custom implementation entirely based on AWS serverless stack + Braintree payment. Although in retrospective I would probably go with Shopify + custom plugin.
Regarding Instagram approval I had no problems with getting approved. I may change now after Facebook replaced Instagram API with their own. However, we had a lot of problems getting prod approval from Braintree Payments. It took me over 1 month to finally be able to process payments.
> I’d also love to see a future where we can just plug in a normal image tag and have all those image processing features out of the box.
This would be great. Currently, headless CMSs are doing this pretty well (for example, Sanity: https://www.sanity.io/docs/presenting-images) but I could see tools like Gatsby offering that too.
> I don’t see Gatsby offering much of a value proposition to people hoping to use it commercially, but I think that paradigm shifts, like PWA becoming a standard that customers will begin to demand from their sites or an increase in the popularity of Gatsby themes leading to a much faster development workflows, could easily help Gatsby overcome some of the competitors it is facing in various areas.
Your points about NextJS are valid but I think there is plenty of room for a few different static site generators to live and thrive in the ecosystem. Even if the differences are small and you can do the same thing on multiple platforms I for one hope we have multiple platforms competing and doing well, the competition will lead to faster innovation and ultimately better tooling for developers.
> Video is hard to get right, with quirks across many combinations of platform/device/OS/browser version/video card/playback resolution/format features
Video is really hard to get right, a Hollywood-style big bang launch on day 1 is difficult to pull off for any software, let alone video.
I feel for the engineers working there, I wonder what the meetings were like last week, did the engineers know they were not prepared for this?
I thought this was a clever way to use Netlify Functions to sign URLs, set the <video> src to the Netlify function, sign the URL and respond with a 302 (also verify the request with CORS headers)
I've heard that Instagram oauth access can be difficult to get approved for production use, were they giving you a tough time when you went through the approval process.