Q: 1.
Did you though about integrating with https://pages.cloudflare.com/ , https://www.netlify.com/ , https://pages.github.com/ , https://render.com/docs/static-sites , https://surge.sh/ or https://vercel.com/ ?
This way you can provide free hosting for static sites to your users at no cost to you. It could be possible to use it only in Creator Pro plan so you can still earn for providing this functionality.
2. What are traffic allowances on your deployment plans?
Thank you for coming with idea to create Buzzy and actually creating it.
Buzzy04726
May 14, 2024A: Hi Matrixik,
Thanks for the questions
Re #1) Buzzy is dynamic with a database and allows you to create sophisticated reactive interfaces. For example, if creating a chat app, it’s only sending delta’s across the wire using websockets. So the static hosting options won’t be able to support the tech.
Under the covers, The Buzzy sever is scalable nodejs server sitting on a mongodb cluster deployed in a kubernetes environment. This is going to give scalability and redundancy if you need to scale up the solution. The nice thing is you don’t have to worry about the tech, we take care of it.
In the past we provided the Docker images for you to deploy, but for the solution here we’re trying to keep it as simple as possible.
There reality is we’ve negotiated a pretty good hosting deal, which allows us to pass on the cost savings. So you probably won’t save a lot hosting it yourself.
What we can do here is offer early adopter Sumolings who buy this deal a FOREVER discount.
For traffic, what sort of traffic are you looking at?
We do have an option to configure a cdn for files
Matrixik
Verified purchaser
Traffic to the internet (outbound transfer), Digitalocean Droplet Transfer Limit is for example 1TB but they App Platform have way less outbound transfer included in standard price and they charge for every GB over it.
Verified purchaser
I was thinking more about only generating front-end code from Figma that doesn't need back-end part (so static site generated from Figma design). This could be used as a example to allow designer/UX person to create and update landing pages looking however they want without programmers involved.
@Matrixik sorry I can't seem to reply to your reply, only one level deep.. so in response to generating front-end code. Sorry we don't do it.
our reasoning for this is :
1) you still need to complete the bulk of development to make things work - for example, the databinding, business logic, database design, security models... there's a lot more coding, cost and effort in that than just the front end code.
It gets even more complicated when you go native mobile and you start dealing with realtime and offline interaction transactions and native specific capabilities like push notifications, geolocaiton, tracking, bluetooth integration.
So we take away that pain. Sure if you have dev teams, time budget there are tools that do that.
2) The peril with code generation tools that allow the developer to fork the code is it becomes a nightmare to maintain and deal with things like bug fixes. Let's say we fix a bug or add a new feature the day/week/or month you have forked the code, merging those code changes back in is going to be horrible, even with source control.
So again the pro of not providing source code, is you get those improvements and bug fixes for free - we do the work, we maintain it
While there's a reliance it becomes total cost of ownership (TCO) question and given out low price point... we're spreading the full time cost of many developer years and low fraction of the cost.
So it's something folk definitely should way up... we just think the the TCO of this massively lower than going down a coding path.
I hope that gives some insight on why we've gone down the path/approach.
replaying to the DigitalOcean data transfer. It probably makes sense to jump on a call to understand more, if you're up for that? We're running on the DO K8s, so not App Platform we have options to use CDNs in the config. For example, cloudImage and there are lots of options here we can include in a specific server's config,
Additionally, files/images are stored in an S3 compatible store, so in general these are direct to client so are not coming through the Buzzy server. This files can be CDN-ed, as above.
The data itself tends to be small and we're doing some smart stuff with websockets so only sending "diffs" of data in realtime.
Additionally in the native app, things get cached locally and for certain use cases like offline map tile you can download the tile files directly from S3.
FYI - there's a landing page sample here https://www.figma.com/community/file/1063666205772519908
Verified purchaser
Thank you for all replies.