AppSheet vs. Bonita Platform

Suitable for database work. Access controller for personnel, products, sales, distribution, etc. Not suitable for applications that require visual and graphic demands. There are graphically interactive applications that have buttons or action gestures that are not common. It should be possible, to create the App. Remove information relevant to the specific company or business for which the App was generated. And then be able to share it with other similar businesses independently.

Well suited for low code/no code applications centered around approval flows. It has built-in task management for users to see their pending actions, comments, statuses, etc. It has a very nice design for process flows. Less appropriate may be for generic type applications with complex screens and logic within those screens that need a lot of data to process.

Incentivized

• Calculations - I have several apps that do some pretty complicated calculations, and decision making to build things like Shopping Lists for a Kanban assembly team, where the app will help a stocker determine whats low in a kanban assembly line stock box.
• Document generation and record keeping - I have an app that users digitally sign and receive PDF contracts, and the system automatically records all records from the transaction. Everything is held in files on YOUR OWN DRIVE (Google Drive) so when you're done with the project or AppSheet you DONT loose your data.
• Client/Customer Management - I follow the old school "Swimming with Sharks" model for client retention and customer engagement, and have built several small customer tracking tools for local businesses. This tool is limited ONLY by your imagine and desire to learn.

Incentivized

• Efficient and fast prototyping: a process can be modeled and tried out quickly and with low investment.
• Full stack prototyping for development and implementation allows the process to be developed and implemented as an application from the prototype. It's not just drawings and wire frames that are tossed over the wall to developers.
• Data modeling is integral from the beginning of the prototype which is appropriate for the stakeholders in the beginning.

Incentivized

• GPS on the maps are terrible. We dont use the map to collect data as the signal is erratic only in Appsheet. We have another app installed on the same phone to get X,Y data which is copied and pasted into the appsheet solution. We have tried everything but Appsheet map and coordinate accuracy and erratic behaviour is below par.
• Deployment management. While it is great that people see your changes right away, it sometimes leads to downtime if one makes a mistake. In the beginning it was hard to tell which changes would negatively effect the users and in some cases the data got jumbled due to table changes. Would be good if development, testing and deployment were better streamlined. No need for auto testing (like selenium etc.) just a place we can test before deploying. Now we have several "dev" versions with a cumbersome copy and paste system.

• There is only one business data model. Even if deploying new processes does not require stopping the platform, the BDM update requires it.
• During the platform evolution often new bugs were introduced so it was risky to deploy the platform in the low minor version. For example, there were memory leaks from 7.2.0 to 7.2.3.
• The administrator portal could be improved. It is hard to look at subprocess data, for example and it is sometimes better to investigate with SQL queries. I don't like new (7.3) task list either.

Incentivized

We are still less than 10 users and probably may continue to be so. But, this being a franchisor set up, could be of use to other users like us.

We just renewed our license

Incentivized

It's just great. The usability is the best thing about Appsheet. You must choose which things will really be used later. You have to be careful of not generating something too big and then it feels like something that need to be learned. This is something that resolve problems, but you had to be able to think before doing. It will not solve problems itself. You need to find the problem, think a solution, and then use appsheet to make this solution a reality

Incentivized

Bonita Platform has allowed us to develop GUI relatively fast using its UI Designer while being able to seamlessly integrate our business logic in Java in a BPMN2 process diagram. It gives a nice productivity boost but still requires programming know-how to be able to deliver the final solution to your business problems.

Incentivized

Engine itself is efficient enough for most cases I dealt with. It can also be extended by clustering. I have done performance tests with JMeter and only managed to induce the crash of... JMeter. If there are efficiency issues they usually concern bad design/implementation of created apps or bottlenecks in integrated systems. Although I have met two cases with efficiency loss.

1. Java 7 related PermGen saturation caused by big number of installed apps (there is no jar dependency reusal between apps option).

2. Big number of waiting event handlers in processes stresses the database.

Incentivized

AppSsheet has a support group and they show videos to help app builders. Though I have truck drivers' hours and can't join the webinars. Support groups with better assists me on a Saturday evening or a Sunday that I have time off. It's hard to watch videos driving down the highway.

It was sometimes difficult to get support on Bonita API.

Incentivized

I did everything on my own

Incentivized

Nothing in particular

Incentivized

We started to try Glide, but we had already started our learning curve with Appsheet, and as the cost is part of our plan, the choice was easy. Since there is no cost for each feature we want to develop, Appsheet can serve as a replacement for tools like Docs, Sheets, and Slides. It just turns into another piece of software the employees are using, so thinking of moving to another product is nonsense.

Incentivized

RHPAM is maybe a very good BPM process engine but is very limited to build a complete application.

We also try site soft W4 which needs more developments to build an application. We finally choose Bonita which is easier to get ready with.

Incentivized

Respect of BPMN standard over the long term. Good enhancements by Bonitasoft for new use cases, for example the introduction of a real form editor even if it has been technically difficult to manage. Once done though, we have far greater possibility of human interaction.

Incentivized

• A good impact in general at the beginning since the free version allows great development so the investment in the implementation is of knowledge and time.
• As a consultant I have expanded my services through this platform including new low code application building services.

• We've had serious problems with 'automated' processes in earlier versions of Bonita (via Talend), especially with connectors. In Bonita 7 we replaced these with REST calls, hoping for better performance.
• Overall, using Bonita has not had a positive impact on our development efficiency. Moving from Talend (using Bonita 5) to Bonita 7 has improved this somewhat. Still, it remains a pain to integrate Bonita in the development and delivery process.
• Migrating from Bonita 7.0 to 7.1 has proven to be a difficult undertaking, mainly on the database level. This has cost us a lot of time and better support would be welcomed.

Incentivized