In the three and a half years since Livepeer first embarked on its mission to build the world’s open video infrastructure, the project has grown into a global network represented by thousands of tokenholders, video miners, and open source contributors.
Today, video developers are beginning to seize on the opportunity to build applications on this network, one with enough GPU capacity to encode all the realtime video streaming through Twitch, Facebook, and YouTube combined, reliably, at scale and at an order of magnitude cheaper price compared to traditional centralized cloud providers.
Over the past few months, we’ve added a bunch of new features and improvements to The Livepeer Explorer. In this post I highlight a few of them and share what’s coming up.
Tokenholders can now stake, vote, and explore orchestrator campaigns directly from their mobile device.
The explorer now has a much more user-friendly transaction UX including confirmation times and gas estimations.
We love Next.js. It’s empowered our team to deliver products and experiences on behalf of our clients with incredible performance, user experience, developer experience, and velocity with its myriad of features such as server rendering, static exporting, CSS-in-JSS support, zero-setup, and extensibility.
We’re also big fans of GraphQL. Declarative data fetching alongside our components and the ability to replace inflexible APIs with a single versatile query system has made data and state management dare I say…delightful.
Given our affinity for and experience with both of these technologies, a few months ago we decided to apply them to one of our…
This year marked the beginning of a fundamental shift in the way I build applications. Thanks to GraphQL and a technique known as universal rendering (also known as isomorphic rendering), I’ve completely changed the way I interact with and render data inside my applications for the better.
This shift, however, was not without its challenges. When I first adopted GraphQL and universal rendering in my development practice, I found myself spending far more time setting up build processes than I was building actual applications. There were so many added complexities I had to deal with for the sake of performance.