11–20 of 33 posts
However, are you sure that you can scale with only 5$ for the "unlimited" plan?
I can imagine large bodies of JSON having to be parsed, could clog up quite a lot. Example: 33kb bodies, that would be +30GB of data exchange at 1M requests.
Looks like you got the hug of death >FirebaseError: Firebase: Exceeded daily quota for email sign-in. (auth/quota-exceeded).
Well... this is why I dropped on HN where people are a bit more forgiving =)
Edit: You know what would be lovely... if Firebase told ME that I'd hit that rate-limit rather than only telling you haha.
No email, not notification in the portal, just failing silently into the night...
Anyway - should be fixed now.
This looks great, reminds me of Yahoo pipes! However, are you sure that you can scale with only 5$ for the "unlimited" plan? I can imagine large bodies of JSON having to be parsed, could clog up quite a lot. Example: 33kb bodies, that would be +30GB of data exchange at 1M requests.
The current thinking is that the $5 tier would end up having a small set of "fair use" restrictions on it for things like max request payload, max workflow execution time, etc. Payload size is the big one, I'm less worried about execution time as the underlying engine that executes the logic is all Async & non-blocking so it's pretty efficient.
I want to have a very clear line though between the allowances that are restricted to encourage a higher price-point (workflows, node's, executions), vs the one's that are there to ensure things don't explode.
The benchmark goal would be for raw compute to equate to At this early stage, I'd probably say that anyone who's processing 1M requests with 33kb bodies each prooobably isn't my initial target customer haha.
Had the same idea for a while, cool that you launched! I would double/triple the price though
The idea being that for a lot of "productivity SaaS apps", one of the biggest friction points is the pain of having to expense the subscription on a corporate card or get it reimbursed via your work - so a $5 price basically side-steps that by being cheap enough that people will just say "fuck it" and pay for it themselves because it saves them an hour a month.
I kinda have a theory that anything over $10 a month and people start to go "hmmm do I really need this?" where as less than $10 a month and people will just impulse buy.
All that being said... price is definitely something I'd experiment with once I validate there's actually real demand.
How does it compare to Node Red? https://nodered.org
IMO it's a lot easier to use than NR (I've played around with NR quite a bit), which is the biggest difference in my opinion. Obviously you don't have to host it, which is a big plus. But the interface is also just a lot more user-friendly and intuitive.
Passing data from one node to another in NR is not super intuitive, and you can't easily visualise data flow coming from multiple sources and then converging into a single node.
As far as I'm aware, NR also doesn't have any kind of Type system - Types in G-Script help to lower the learning curve because it's a bit like building a PC... if the cable fits in the port, there's a pretty good chance it will atleast work and not explode.
NR does support "code reuse" too, but again it's just not super intuitive and user-friendly. To be clear, there's nothing G-Script does that hasn't been done before, but IMO it's packages in a very user-friendly format and priced very competitively.
I'm looking to add super simple Auth, Testing, and Data Persistence over the next few weeks, which I think will accentuate that usability gap even more.
This is nice! As someone who has dived into Unreal Engine and learned Blueprint, I realize the power Visual programming brings to the table. It's pretty efficient, a great fun way to write logic and I believe it's the future in a way too.
Nice implementation and kudos for having modules capabilities from the start.
I suggest looking at other products for visual programming Web Applications like OutSystems, or PowerApps. Nice implementation and kudos for having modules capabilities from the start.
1. Simplicity - both of those things you mention are painstakingly unintuitive if you want to do something fairly complex.
2. Price - Power Automate gets stupidly expensive at any kind of scale, the base plan is only $15 a month, but its capped at 5000 executions. Similarly, OutSystems gets REALLY expensive pretty quickly once you get over the smallest size plan.