ObjectGears

What do you like best?

I like the fast response and easy start when a need for a new application functionality is identified in the organization. You start with design of necessary data structures, then define roles and screens. That is something you can present to your colleages and get their buying to work on common goal. As you progress and formulate detailed needs, you define business rules, reports, workflows and interfaces to other applications. Having most functionality on click breaks the barrier between developer and user of the application.

What do you dislike?

At a certain point of time you may realize that you need to do some coding. However, I see it rather as an potential to extend to things that cannot be configured just by clicking. Vast majority of the development stays in clicking and therefore open to no-coders.

What problems are you solving with the product? What benefits have you realized?

Apart from IT processes and Knowledge management that are included in the initial pack, we use it for many small agendas. We also started to use it as a central master data repository interfacing with other systems.