Show HN: Superblocks – IDE for Internal Apps, APIs and Cron Jobs (superblocks.com)

Is this open source? Btw your demo is really slow on my phone.

Gamechanging. Built an internal admin tool with Superblocks in just a few minutes - definitely saved me hours of time and let me focus on building my core product. Congrats on building an awesome product already.

Super interesting. Is the idea that this is like Retool, but a little more dummy'd down (in a good way) and has cron/workflow capabilities?

What sort of company size would find this useful? I can already see several pushbacks against this type of tool.

How does this compare to Retool (https://retool.com)? We use Retool at my company and like it; this seems like it is similar, but targets non-developers and is less mature (e.g. in the quality of the components)?

yes! more options to save me from powerapps. looks good so far.

As someone who used to have to hack internal tools, love that superblocks is making this easier!

Super cool. It's likely in the works but it would be cool to have more recipes / mini templates to start with on the application builder. E.g. a list of most active users or something similarly generic to help me get to something real faster. Also the ability to add an integration / connect postgres from the 'new api' prompt rather than having to go back to the dashboard first

Super exciting. What industries or applications are you guys tackling first? Congrats!

beautiful. Looks really great!!

I like the UI integration. Feels similar in purpose to UIPath or other robotic process automation systems, but I don't have enough experience to compare.

Looking at the video, at 1:02 you do put in code to open yourself to SQL injection... it's for internal tools, but still...

Looks awesome, internal tools are usually such a pain to build and maintain (and tough to prioritize relative to customer-facing features). Excited to see this!

I never watch videos (I can't skim read a video and they usually involve audio and that's usually inconvenient).

So without the video I'm struggling to understand what "programming" with superblocks means. Is it drag and drop visual programming? Show me a screengrab. Is it coding? What does the syntax look like?

Is it a mixture of both? I want to see both.

Yes - I'm lazy and probably could have read more but lazy, busy people are good test subjects as they probably make up the majority of eyeballs.

We are glad to be one of Superblock's early customers to build some of our internal tools and are super happy about it. Congrats on your official launch.

I have been actively following this space. I think there is a huge fallacy in a tool like this. At surface most of the developers love the idea, you often get feedback that people would use it but time comes people just not integrate their service with a platform like this. You have to build huge amount of trust either by raising from popular VC, Angel's, blogpost by reputed dev advocates, socialproofing. For a general purpose framework it is generally an uphill battle. Having said that, there has been outcomes in past like rundeck's acquisition by pagerduty. One thing I noticed that platform who have built some features that bound them to certain usecases done really well. Platform with a horizontal is a very long road than a platform with certain purpose, it also makes it easy to sell. Just some thoughts.

Given the comments I'm used to seeing in general in HN, the over excited tone of the comments in this post makes me wonder how truthful all the praising is, or if they are related to the company in any way. Maybe HN is actually full of people who build internal tools and find this honestly awesome and a game changer.

What’s the lock-in? As in - when we’ve built a UI/app is it locked into a subscription?

What happens if you go out of business or we stop subscribing?

This could be really useful in healthtech, is it HIPAA compliant by any chance?

Looks like it has tons of potential, but from watching your demo, developing steps using a bunch of form fields is going to be very tedious, especially when you're trying to test/debug things and have to flip between screens constantly.

Looks great. Might be simplifying too much but is it basically like Retool + cron jobs? Super interesting if that's the case :)

Congrats! Seems like a Retool competitor but focused more on developers? I'm not sure if that's the direction I would go since developers already have pretty good tooling for their level of expertise, IMO.

Although, I could see how building an app that uses data across the various SaaS tools a company uses without requiring that data to be dumped into another database could be useful. Maybe I'm missing the point.

As an aside, I'd love to see Retool but for less technical people. Specifically, a way to make Google Sheets available for multiple people in a company to use. We have multiple quick and dirty "calculators" (think pricing for sales, comp for recruiting) that we roll out across our company. Eventually they get operationalized and converted into proper applications (or we buy a SaaS product for it) but would be nice to have an interim solution. Some requirements:

- Ability to create a very simple CRUD web UI

- Authz/n with ability for IT to integrate into their SSO.

- Google Sheets backend and integration so financial analysts can update and manage.

The code snippet in this [0] example from the index page (top) looks to have an f-string issue:

return [

  {

    "message": "{t.name} is due for {t.due_days} days",

    "assignee": t.assignee,

  }

  for t in tickets

]

[0] https://assets-global.website-files.com/627d359d0e0aa265b781...

E: Fix formatting (TIL HN doesn't support code blocks)

[Disclaimer: my company is using Superblocks and have been paying for it for about a year]

Been reading the comments and I think there are a bunch of questions about why companies would use a tool like this and that integrating your product / company into it is potentially risky. Here's why we decided to use it.

First thing you should know is that before we moved to Superblocks, we were using a combination of Retool, Google Cloud Scheduler, Mode Analytics, and a few small Google App Engine apps to solve our problems.

There is a whole ecosystem of apps and mini-products our engineering team has to build which require slow-paced maintenance, but are still mission critical to our business. Analytics dashboards, Slack reporters, revenue dashboards, customer service dashboards, Discord bots, etc.

There are plenty of different tools which solve some of those problems in silo, but the main problem (and beauty) of building internal apps is that you can fully solve for your unique business problem. We're a tech-enabled advertising agency (there are a handful of companies like ours in the world) and we both have our own external product as well as a series of internal apps that power our operations.

We decided to move all our internal apps to Superblocks effectively because we could merge a few different platform layer things (Google Cloud Scheduler, App Engine, Mode, Retool) and be able to build much faster within our team. The big thing for us was that we have engineers writing in Python (more data heavy stuff), and engineers writing Javascript. Previously, we had to have them offer APIs to each other and it wasn't as agile as it is today for simple things we had to build for our business stakeholders.

I remember seeing one of our first Workflows on Superblocks when our data scientist built a BigQuery step, a Python step, and then our Javascript engineers grabbing that to do some post-processing with it to display the data and thinking "this is probably how most tiny apps will get built in the future".

I don't want to have infrastructure for every tiny solution I built for our team. I just want things to work.

Interesting. This is kind of like Camunda without the BPMN baggage and a full blown IDE that integrates all the frontend/UI aspects with the backend workflow stuff. With Camunda, you have to build your own frontend past the auto-generated task forms. It’d also be interesting to see what a rule engine would look like in Superblocks.

You say source-available, but I do wonder what happens with all your apps/workflows if Superblocks goes belly up. It doesn't seem like there’d be an easy way to migrate off it. With Camunda, their modeler and engine is open source and all the code you write is like any other code—it exists in your own git repo.

(PS: Not a Camunda shill, but have built proofs-of-concept with it in the past, and am evaluating it again.)