Why The Application-Centric Design in Joget Workflow v3?
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXdT53HzB5Eamqka1dgRngeC2ZvqoWhR0Fug9k00iU3gKIWfviTqVNRHgPfvVHwwRCByQW-5ftU4YWMChpzkSpOORfTOrHpxOVsnYK0x-XBVnSbQNwEExPubA56vjAKIC_pRPSs55Oo2Q/s1600/Joget+Workflow+v3+-+Userview.jpg)
Our previous blog post, Sneak Preview of Joget Workflow v3 , has gotten a lot of attention from Joget Workflow adopters as well as industry watchers in the BPM space. Many people are surprised with the application-centric approach that we are pursuing, but at the same time, the comments and feedbacks we have received have been very encouraging! Why The Application-Centric Design? We have learnt a lot in the 19 months since the public release of v1.0. Based on observing numerous implementations of Joget Workflow, we were able to gather a couple of interesting facts: Process automation is just part of the implementation use case. Most of the time, what a customer actually needs ultimately, is an application. Process automation is just part of the implementation use case. A customer also needs reports in tabular format and the ability to easily export the records . As Joget Workflow's design goal heads towards maximal "simplicity", it doesn't make sense for us not to ad