Should I Build It Should I Build It
10 May 2025
GitHub API Developer Tools

API server that can render video from JSON configuration file

Confidence
Engagement
Net use signal
Net buy signal

Idea type: Run Away

Multiple attempts have failed with clear negative feedback. Continuing down this path would likely waste your time and resources when better opportunities exist elsewhere.

Should You Build It?

Don't build it.

Your are here

Creating an API server for rendering videos from JSON configurations falls into a difficult category. Our analysis reveals that similar ideas haven't gained traction, suggesting significant hurdles or a lack of market demand for this specific approach. The existence of six similar products indicates some level of interest in the general space of programmatic video creation, but the absence of positive 'use' or 'buy' signals and the lack of strong positive feedback among existing similar products suggests fundamental challenges with the core value proposition. This doesn't mean video rendering APIs are doomed, but it does mean your specific approach might need serious rethinking. The criticisms for these products often center around pricing transparency, misleading information, and fundamental technical issues like file compatibility. Before investing more time, deeply analyze why these existing solutions haven't resonated and how your offering can overcome these specific obstacles.

Recommendations

  1. Thoroughly review the negative feedback from similar products. The criticism summary from the 'video editing SDK that runs in the browser' highlights key issues like misleading claims, lack of transparent pricing, and concerns over open-source status. Understanding these pain points is crucial before moving forward.
  2. Explore alternative, related problems that your skills could address. If the core idea of a JSON-configurable video renderer isn't viable, perhaps there's a related need in video processing, automation, or a specific niche application you can uniquely solve. Look for adjacent areas where your technical expertise can be more effectively applied.
  3. If you've already built a prototype, assess whether the underlying technology can be repurposed. Can the rendering engine be adapted for a different use case? Could the API be refocused on a more specific video creation task? Identifying a new application for your existing work can save significant development time.
  4. Conduct in-depth interviews with at least three potential users who've tried similar products. Don't just ask if they like the idea; dig into their workflows, pain points, and unmet needs. Understanding their actual requirements will help you refine your approach and identify opportunities for differentiation.
  5. Based on your research, consider pivoting to a new idea within the broader video creation space. Focus on addressing the specific criticisms and unmet needs you've uncovered. A new direction, informed by user feedback and competitive analysis, is more likely to succeed than persisting with a flawed concept.
  6. Prioritize transparent pricing and clear communication. Address the issues raised in the criticism summary, particularly regarding hidden costs and misleading claims. Clearly outline your pricing structure and product capabilities to build trust with potential users.
  7. Focus on a specific target market with a clear value proposition. Determine the ideal user for your product and tailor your messaging to their specific needs. Avoid trying to be everything to everyone, as this can dilute your message and make it harder to attract the right customers.

Questions

  1. What specific unmet needs in video creation are you uniquely positioned to address, and how does your API server directly solve these problems in a way that existing solutions don't?
  2. Given the criticisms of similar products regarding pricing transparency and open-source claims, how will you ensure your offering is both clear and trustworthy to potential users?
  3. What is the smallest, most specific niche you can target with your API server, and what are the key metrics you'll use to measure success in that niche?

Your are here

Creating an API server for rendering videos from JSON configurations falls into a difficult category. Our analysis reveals that similar ideas haven't gained traction, suggesting significant hurdles or a lack of market demand for this specific approach. The existence of six similar products indicates some level of interest in the general space of programmatic video creation, but the absence of positive 'use' or 'buy' signals and the lack of strong positive feedback among existing similar products suggests fundamental challenges with the core value proposition. This doesn't mean video rendering APIs are doomed, but it does mean your specific approach might need serious rethinking. The criticisms for these products often center around pricing transparency, misleading information, and fundamental technical issues like file compatibility. Before investing more time, deeply analyze why these existing solutions haven't resonated and how your offering can overcome these specific obstacles.

Recommendations

  1. Thoroughly review the negative feedback from similar products. The criticism summary from the 'video editing SDK that runs in the browser' highlights key issues like misleading claims, lack of transparent pricing, and concerns over open-source status. Understanding these pain points is crucial before moving forward.
  2. Explore alternative, related problems that your skills could address. If the core idea of a JSON-configurable video renderer isn't viable, perhaps there's a related need in video processing, automation, or a specific niche application you can uniquely solve. Look for adjacent areas where your technical expertise can be more effectively applied.
  3. If you've already built a prototype, assess whether the underlying technology can be repurposed. Can the rendering engine be adapted for a different use case? Could the API be refocused on a more specific video creation task? Identifying a new application for your existing work can save significant development time.
  4. Conduct in-depth interviews with at least three potential users who've tried similar products. Don't just ask if they like the idea; dig into their workflows, pain points, and unmet needs. Understanding their actual requirements will help you refine your approach and identify opportunities for differentiation.
  5. Based on your research, consider pivoting to a new idea within the broader video creation space. Focus on addressing the specific criticisms and unmet needs you've uncovered. A new direction, informed by user feedback and competitive analysis, is more likely to succeed than persisting with a flawed concept.
  6. Prioritize transparent pricing and clear communication. Address the issues raised in the criticism summary, particularly regarding hidden costs and misleading claims. Clearly outline your pricing structure and product capabilities to build trust with potential users.
  7. Focus on a specific target market with a clear value proposition. Determine the ideal user for your product and tailor your messaging to their specific needs. Avoid trying to be everything to everyone, as this can dilute your message and make it harder to attract the right customers.

Questions

  1. What specific unmet needs in video creation are you uniquely positioned to address, and how does your API server directly solve these problems in a way that existing solutions don't?
  2. Given the criticisms of similar products regarding pricing transparency and open-source claims, how will you ensure your offering is both clear and trustworthy to potential users?
  3. What is the smallest, most specific niche you can target with your API server, and what are the key metrics you'll use to measure success in that niche?

  • Confidence: High
    • Number of similar products: 6
  • Engagement: Medium
    • Average number of comments: 10
  • Net use signal: -5.3%
    • Positive use signal: 11.3%
    • Negative use signal: 16.5%
  • Net buy signal: -15.3%
    • Positive buy signal: 0.0%
    • Negative buy signal: 15.3%

This chart summarizes all the similar products we found for your idea in a single plot.

The x-axis represents the overall feedback each product received. This is calculated from the net use and buy signals that were expressed in the comments. The maximum is +1, which means all comments (across all similar products) were positive, expressed a willingness to use & buy said product. The minimum is -1 and it means the exact opposite.

The y-axis captures the strength of the signal, i.e. how many people commented and how does this rank against other products in this category. The maximum is +1, which means these products were the most liked, upvoted and talked about launches recently. The minimum is 0, meaning zero engagement or feedback was received.

The sizes of the product dots are determined by the relevance to your idea, where 10 is the maximum.

Your idea is the big blueish dot, which should lie somewhere in the polygon defined by these products. It can be off-center because we use custom weighting to summarize these metrics.

Similar products

Relevance

RenderDotVideo – Make videos in the browser (Chromium)

15 Jun 2024 Artificial Intelligence

Hi, I'm Per and I spent the last months on this side project. It's a template engine where you can render and export MP4 videos with sound from your browser. No server involved.If you want to try it out, it costs nothing and you don't need an account.Unfortunately it's Chrome/Chromium only for now.Please check it out if you can :)Per

Avatar
1
1
Relevance

RenderLion - Turn URLs & prompts into videos instantly

05 Nov 2024 Design Tools Artificial Intelligence Marketing

Turn URLs and prompts into jaw-dropping videos instantly. Fast, effortless, stunning results perfectly sized for any platform with just a click!

RenderLion's launch on Product Hunt has generated excitement and positive feedback, with many users eager to try its AI video generator. Users highlight its potential as a game-changer for creating engaging animations from various content types, including daily news and memecoin videos. The platform's easy-to-use interface is also appreciated. Congratulations were extended to Alex and the RenderLion team, with many wishing them luck and success in their future endeavors.

Avatar
77
10
60.0%
10
77
60.0%
Relevance

A video editing SDK that runs in the browser

30 Jul 2024 Developer Tools

Hello HN,Video content is more popular than ever, but the toolkit for creating such content is a bit behind. You usually have to rely on a server for rendering whenever you want to create a video editing project in the browser. This means uploading content to a server, coding complex filters and effects, and more.My friend and I spent a year developing an SDK that handles all these complexities and offers an easy-to-use interface for developers. The SDK works entirely in the browser, manages memory efficiently so it can run even on a 7-year-old Android device, supports GLSL effects and transitions, handles captions, and much more.We also created a custom video editor UI interface using the SDK to showcase its speed and flexibility. You can see the video editor embedded on our landing page: https://rendley.com.As for the tech stack, the SDK was built using TypeScript, Pixi.js, C++, FFmpeg WASM, and WebCodecs. The UI interface was created using Stencil.js and MobX.The SDK is called Rendley SDK and it is live on npm: https://www.npmjs.com/package/@rendley/sdkTo get started, follow this guide: https://docs.rendley.com/installationIf you want to embed the pre-made interface, follow this guide, it’s literally a few lines of code: https://docs.rendley.com/video-editorIf you have any questions about the product or any feedback, feel free to write them below, and I’ll be more than happy to answer them.

Users raised concerns about the product's open source claims, patent issues with mp4, and lack of visible pricing information. Comparisons with similar services like Revideo and Remotion were made, questioning differences in API, rendering, and licensing. Technical issues with ffmpeg wasm, codec support, and file loading were noted. The 'Get in touch' button leading to a 404 page and forced sign-up were criticized. Some users appreciated the service but were deterred by the sales approach and misleading information on the website. There were also requests for transparent pricing and questions about the use of Pixi.js.

Users criticized the product for not being truly open source, misleading claims, and lack of public repositories. Concerns over memory safety, codec errors, and patent issues were noted. The requirement for a license key, forced sign-up, and issues with file compatibility were disliked. Criticisms also focused on the lack of transparent pricing, with many mentioning hidden costs behind email requirements and no fixed pricing. The product's value proposition for non-technical users and small target market were questioned, along with the effectiveness of Show HN/Product Hunt for growth.

Avatar
129
42
-26.2%
-28.6%
42
129
4.8%
Relevance

Open-source streaming API from ingest to player

08 Sep 2024 GitHub API Developer Tools

Hi there HN!I'm Matthias and I've been into video streaming for quite a while now. Over the years I've built plenty of small setups, often CLI tools to test and debug streaming video. About a month ago, during my annual holiday, I started working on a simple API on top of my CLI tools. It's time consuming to craft and run multiple ffmpeg jobs, get GOP / keyframes right, merge playlists, package to HLS, ... One thing led to another and I eventually started exploring HLS interstitials, VMAP / VAST and dynamic ad insertion, MSE / EME (HLS.js in general), React (perf) as a player UI (although I have some experience with that from the past).Once transcode or package jobs are finished, they'll sync back to S3 (or any S3 compliant storage service).From the get go I built in public, including:1. Scale transcode (ffmpeg) jobs over multiple machines, crafting multiple video renditions, audio and text tracks. The API endpoint to start this job is rather simple, you define your source files (what you have, eg; an mp4 as video; an mp4 as audio with language "eng", ...) and the output (streams) of what you want (eg; H264 video 1080p, 720p, aac audio with language "eng", ...).2. Package all transcode streams into an HLS playlist, uses shaka-packager under the hood. Uploads every playlist and segment to S3 publicly, at this point your asset is playable.3. An on-the-fly playlist manipulator where you can limit the max. quality, add HLS interstitials for ad or bumper insertion or use VMAP / VAST to insert ads in stream. When a VAST is not yet transcoded and packaged, stitcher will start that job. When a playlist is found for that particular ad, stitcher will add an interstitial to the playlist. An HLS Interstitials supported player will then be able to play the ad at the given time defined in the VMAP.4. A facade on top of HLS.js that makes working with interstitials a bit easier. Know that interstitials support with HLS.js is ongoing work (https://github.com/video-dev/hls.js/issues/5730).5. When I was toying around, I felt I missed the experience of interacting with a player (that's the only part in video streaming your end users interact with, and the default HTML5 player UI doesn't fit more advanced use cases such as quality selection, display ad points on the seekbar, ...) thus I built a small React component that functions as a player UI on top of the facade I built earlier.I'm having a blast so far. Hope it provides value to some of you. Feedback is appreciated!

Avatar
5
5
Relevance

Typescript library for editing videos with code

17 Aug 2024 GitHub Developer Tools

Today we launched a Typescript library for building video processing applications that can run completely client-sideThis project has been started in March 2023 with the mission of creating the "video processing toolkit for the area of AI". During an extensive research period, we quickly decided to fully embrace WebGPU, which offers a substantial performance improvement over its predecessor WebGL and technologies alike.In combination with WebCodecs, these two technologies lead to unprecedented rendering capabilities on the web and pave the way for the next generation of video processing applicationsWould love to hear your feedback!

Users reported a non-functional close modal button for the sign-in process. One user found the library useful and expressed gratitude. Another user noted that there was no content available.

Users reported that the close modal button is not functioning properly.

Avatar
20
3
33.3%
3
20
33.3%
Top