KPMG Associate Consultant Shivangi Pathak, a developer with more than three years of experience, was first introduced Unqork and codeless development at the end of 2020. Since then, she has earned her Associate and Professional Unqork Configurator certificate, and she was recently named an Unqork Community subject matter expert (SME) as one of the community's most active and knowledgeable members.
Shivangi explains how Unqork helps her build sophisticated enterprise apps more quickly, shares best practices with fellow Creators, and tells us about her submission for the 2022 Unqork Creator Hackathon.
You can watch Shivangi and the other winners of the 2022 Unqork Creator Hackathon discussing their entries here.
Tell us about your award-winning submission for the 2022 Unqork Creator Hackathon.
Shivangi: Basically, I created an application that serves as a book club. It is a book review app that includes a list of books and enables book fans to select a title, write a review, and add related images. It also has embedded translation capabilities via Google’s Translate, if users get stuck on a word and need help. Users can also add books that aren’t currently in the app, then write reviews, post images, and rate the book.
Tell us about some of the more exciting client projects you’ve created with Unqork?
Right after completing my initial Unqork training, I started working on a digital front door for a major healthcare provider. It was a vast project with many parts, and that was great, because I got to learn so many things.
Currently, I am working on a project for an insurance provider that automates and streamlines the valuations and asset management processes. It has a centralized workflow that allows users to upload documents and data, and go through all the valuation details.
I like the fact that with Unqork you are not restricted to one business domain. It lets you work on a wide variety of projects and applications.
Did you draw on capabilities in the platform or in Unqork Marketplace to think more creatively about your projects?
The freeform grid capability that Unqork recently added was a big help. It lets you nest many components with one component—even a whole grid inside a grid. This nesting of components gives you much more flexibility. And Unqork Marketplace has so many services that are easy to use, so you have a lot to choose from!
How does your experience working with Unqork differ from other low-code/no-code platforms?
With the other platforms I have used, you have to have some knowledge of coding. Coding is part of the development process. With Unqork, you can start configuring even if you have no knowledge of code at all.
I would also say that, in my experience, data processing and logic manipulation are much easier in Unqork. You just drag and drop, and you have all the information you need related to components and operators.
Finally, with Unqork API consumption becomes easy. Once you start building in Unqork, you really see that.
"The ease of third-party integrations is the most beautiful aspect of the Unqork platform for me."
What are your favorite things about Unqork?
The ease of third-party integrations is the most beautiful aspect of the Unqork platform for me.
Second, I would have to say the architectural management aspect of Unqork. It gives you a really clear vision of your project. This lets you move forward with a sense of security about what you are building.
Third, I would mention Unqork’s cloud-based architecture. You don’t need to worry about the other computing resources your applications are drawing on, so it is much easier to achieve your goals.
And finally, the cherry on the cake is the availability of all the snippets, which are reusable pieces of commonly-used functions that you can just drag and drop into the application you’re building.
Do you have any best practices you would like to share with other Creators?
First of all, I definitely recommend that you establish your API architecture right at the beginning. Otherwise, you end up having to conduct a configuration analysis later on, and you get stuck fixing a bunch of things.
When it comes to role-based accesses, I would also recommend that you build that into the component level, rather than the module level. Not only does this make your work easier, but you also help make the application more secure.