Budibase vs. Skuid

Even though its a solid tool I think for now it is best suited to create some relatively complex apps but not best suited to build very complex apps where you need to manipulate data during runtime. But they are actively developing the produt and push updates on the regular basis which makes me feel optimistic about their future.

Incentivized

For anyone looking to build customized user experiences quickly on Salesforce.com and who don't have access or budget for developers then Skuid is an excellent option. Although some investment in license costs and learning is required the pay off comes with the sheer speed and volume of applications that can be built and delivered to the business in short time frames.

Incentivized

• Can connect REST APIs
• Can define User Roles
• Open Source so you can host it yourself if you prefer
• They have a component called reapeater field which is extreamly useful in cases you want to iterate UI component on you table

Incentivized

• Pulling data from external sources.
• Providing visualizations that tell a story & summarize.
• Integrations with other applications, i.e. Sharepoint for document library storage.
• Amazing support! Very quick to respond and also wonderful to work with when scoping out your needs.

Incentivized

• Building UI even though simple, it gets tougher when you want to build a complex one. The way they have implemented data sources in the UI is bit rigid.
• you can not use JS in all the components to manipulate data which makes it less dynamic compared to say AppSmith.

Incentivized

• Release management. Whenever a new version of Skuid is released, upgrading can be a dubious task.
• Support. Skuid does not offer standard support. Instead, you will be required to use the Skuid community or purchase engineering hours.

Incentivized

Incentivized

Salesforce Flows was another way of accomplishing some goals we had but Skuid was much simpler to set up, more intuitive for users, and faster to run. We didn't experience any Apex exceptions or query limits. The only downside to using Skuid vs. Flows was that Skuid required developers whereas Flows can be done by an administrator.

Incentivized

• made building internal tool easy
• saved good number of man hours compared to building tools from scratch

Incentivized

• Our customers have been very happy with Skuid and it has allowed them to do things that otherwise would have been impossible.

Incentivized