504,105 visitors this month

Latest reviews

RHRhea Vandermeer3d ago
I put off making a product video for about six months because every previous attempt turned into an afternoon in an editor. Recorded the screen capture, dropped it in, picked a template and had something I was not embarrassed by in under an hour. The part that actually saved me was the automatic captions — most people watch these on mute and I would not have bothered otherwise. My one complaint is that the template choice matters more than it looks like it does; the first one I picked made everything feel like an advert.
Typeframes
TOTobias Lindqvist9d ago
Set this up for a small open source project after people kept asking where they could send something. Took about ten minutes and the first support came through the same week. What works is that supporters do not need an account — that single thing removes most of the drop-off I saw with the alternative I tried first. Payouts have been on schedule. Marking it four rather than five because the analytics are thin; I would like to know where people are arriving from and I cannot tell.
Buy Me a Coffee
MAMarguerite Osei15d ago
Been using this for about four months for content planning. It is genuinely good at surfacing things I would not have thought to look for, and a couple of those became our best-performing posts of the quarter. Worth being realistic about what the numbers are though. The growth figures are directional rather than exact, and I have seen a few topics flagged as rising that were really one large news cycle. I treat it as a list of things to go investigate rather than a list of things to go write, and on that basis it earns its cost.
Exploding Topics
DEDevashish Raman22d ago
I have used this on every backend project for years and it is still the first thing I install. Collections shared across the team save a genuine amount of onboarding time, and the scripting is powerful enough that we run a decent chunk of our integration checks through it. The honest criticism is that it has grown a lot. What was a fast request client now takes a while to start and pushes cloud features I do not want. It is still the tool I reach for; I just notice the weight now in a way I did not three years ago.
Postman
PRPriyanka Balachandran1mo ago
Moved a marketing site and two documentation sites over last year. The thing I did not expect to care about was deploy previews on every pull request — being able to send a designer a working link instead of a screenshot changed how our review process works. Rollbacks are one click and have saved me twice. Build minutes are the thing to watch on the pricing side; our docs site rebuilds often and we hit the limit faster than I planned for, so check that before committing if you deploy frequently.
Netlify

App Builders

Building apps and internal tools without code.

Nothing launched in this category yet.

About App Builders

Building an application without writing code has become genuinely viable for a specific and identifiable class of problem: internal tools, admin interfaces, forms over a database, dashboards, approval workflows and the long tail of small applications that a business needs and cannot justify an engineering quarter for. Within that class the tools here are excellent. Outside it they get expensive in ways that are hard to see at the start.

The reliable signal for whether your problem fits is how much of the application is standard interaction with structured data. If it is mostly lists, forms, filters, roles and notifications, a builder will get you there quickly and the result will be maintainable. If the value is in unusual interaction, heavy computation, or logic with many interacting conditions, you will spend your time fighting the abstraction, and the escape hatch — dropping into code inside the platform — usually turns out to be the least pleasant place to write code.

The internal-tools group specifically is the strongest part of this subcategory, because the requirements are known: connect to an existing database or API, generate a usable interface, add permissions, deploy behind your login. Tools built for exactly that do it very well, and the alternative is genuinely months of engineering time on something no customer sees.

Data is the part to think about first and the part most people think about last. Where does it live, who can reach it, and can you query it with anything other than this tool? Applications built on a platform's internal database are the hardest to leave. Ones built on your own database, with the builder providing only the interface, are straightforward to replace and are the better architecture where possible.

Cost usually scales per editor seat, per end user, or per run of an automation, and per-end-user pricing is the one that surprises people. Model the bill at ten times your current usage before committing, because migration once a tool is embedded in a business process is a project rather than a decision.

Check the version control and environment story too. A builder with no way to test a change before it reaches the people relying on it will eventually cost you an outage in a process that matters.