If you have been following DhiWise, you would know what we bring to the table. It’s not just a platform to help you build apps quicker. Instead, at DhiWise, we focus on making speed and quality the ways of ‘coding’ life— allowing developers to look at speed and cost savings instead of all that grunt.
And yes, we started all right. Created a base, planned ahead, and even worked on our insightful and knowledge-packed launch weeks. Yet, we wanted to do more. That is exactly why we took up the “30-day30-use-cases” challenge on 29th August 2022, to ensure that every user can get a feel of DhiWise’s capabilities in real-time.
We believe there are already enough SaaS products that tell you what to do. With the “30-day30-use-cases,”— we planned to show you the ‘how’ they often miss out on. So buckle up and prepare to onboard this real-time building marathon that extended for 30 days— 6 weeks straight. This blog collates each of the 30 use cases with a detailed brief and other relevant resources.
Day 1 started us playing around with the concept of an eCommerce application. But wait, don’t we need a top-notch production-quality design, auth access, navigation support to move from one screen to another, and a slew of other resources to get an eCommerce app to fruition? Actually, one such app needs a lot more:
Problem statement: An eCommerce application must feature detailed products and support categories, offer seamless login options, present live info, and even have strategies to negate app crashes. And building an app of that stature requires time and money.
Solution: Saloni Saraiya, developer at DhiWise, used the in-house Flutter builder, Webflow APIs (a CMS with responsive design elements), and Firebase authentication for data and logins to build a production-quality grocery application.
Here is how she managed that:
Day 2 was all about the challenges enterprises face— data/ record handling being the biggest of them all. Yet, creating something that would manage every office data set doesn’t come easy. Here is why:
Problem statement: Any office-specific app you plan to build would need a collaborative design, proper REST internal APIs to pull data from diverse departments, and obviously some logic-led navigations. That would also need a lot of time, with manual coding, API integrations, and other needs involved.
Solution: Prem Danej, a developer at DhiWise, managed to work around the problem by using DhiWise’s Flutter builder. He worked alongside the Airtable APIs (platform for handling relational databases) and deployed the DhiWise-Figma relationship to build an office inventory app in virtually no time.
Here is how Prem went about this use case:
We all know what Notion— the thought aggregating platform—is capable of. What if the capabilities of Notion were to be included and deployed as a mobile application? Sounds unreal, right?
Problem statement: To prepare an app as interactive as Notion itself, authorization, API integrations, support for notifications, code quality, data collection, and other facets would require attention. Handling each of the mentioned aspects would require a lot of time.
Solution: Kajal Morker, developer at DhiWise, intuitively used the Flutter builder and Notion APIs to quickly prepare the second-brain application. DhiWise took care of the design to code conversion, auth setup, navigations, and other aspects— helping save a lot of time— 128 hours, to be exact.
Here is how she went about this use case:
Imagine building an applicant tracking, employee onboarding, and time-management application for your organization. More of a one-stop intranet solution. No, not some third-party outsourcing of services but a dedicated app that’s fast and scalable. Sounds fun, but there are a few issues:
Problem statement: Data storage needs to be handled efficiently. Proper authorization and accessibility would then be the key requirements for developing such an application.
Solution: The problem wasn’t big enough for Jemee Tala— developer at DhiWise, as she deployed DhiWise’s React builder and Freshteam APIs to build the said app in no time. She seamlessly used Supabase APIs for data and authorization to make the application a reality.
Figma is cool but doesn’t have the best accessibility in place. A curated app with Figma functionality and social sharing support would be great. But there is a catch!
Problem statement: The process would need you to cover every Figma-related process: finding designs, copying links, switching back to the platform of choice, and more. Covering each base would cost you hours.
Here is how things unpacked!
Pro traders have been looking for a resourceful trading application. However, creating a full-blown app that can handle trading isn’t easy. It’s not just about the app; even the notification module needs to be top-notch. But that’s not all.
Problem statement: For building a trading app from scratch, it is necessary to focus on the holistic aspect of trading: strategies, plans, and tracking purchases. And the user needs to be informed via messages. Quite a lot to do, right?
Here is how it all went down:
Have you ever wanted a Spotify-like app all to yourself? And what if I said that the application could find tracks for you based on your emotions? Easier said than done!
Problem statement: Developing such an app requires the best possible UI, user experience, live info, documentation-rich API access, and other resources. Addressing each aspect would take a lot of time, won’t it?
Solution: In comes a new music application, developed by Zaiynab Mansuri— developer at DhiWise, using the React builder, saving over 120 hours in the process. This application was developed as a part of DhiWise’s “30-day30-use-case” initiative, helping people track and listen to music. The process used Spotify APIs to request music tracks based on emoji-specific emotion-tracking triggers.
Here is what the entire development lifecycle looked like:
As an enterprise, how do you monitor services within the organization, especially when one service depends on the other. That is the point when you look for a one-stop app for monitoring notifications, downtime, and more. Yet, building the same is harder than ideating.
Problem statement: Multiple dependencies would require access to multiple internal APIs. Nesting would be required as one service might depend on two other completely different services. Coding for all of that sounds time intensive.
Solution: What if there was a web app that could use the React builder, Slack webhook APIs for notifications and intimations, and service status APIs and work holistically to offer all the relevant information? One such tool was developed by Ashutosh Dave— a developer at DhiWise.
Here is what the entire process looked like!
A day before, we took care of a web app focusing on service status checks. But that just didn’t feel enough. We had to do something for the mobile apps, and what could be better than to put the DhiWise Flutter builder to work?
Problem statement: With standard coding practices, it would take a lot of time to connect different services. Plus, sending notifications internally would require another set of implementations.
Solution: However, Ashutosh Dave— a developer at DhiWise— had other ideas. He managed to pair Sslack webhook APIs alongside the diverse service status APIs to create a one-stop status-checking app with ease.
Sharing tweets over WhatsApp was always frustrating. A Twitter user would know that you got to share one tweet at once— making the process painstakingly slow. But there is more to solving this issue than building a multi-tweet sharing app.
Problem statement: Any app you build would need an interactive UI/UX. Also, accessing Twitter using a standard application would again mean one-by-one tweet sharing. Creating a UI, finding the right APIs, coding, and more can be time intensive.
Solution: Rakesh Purohit— developer at DhiWise— made life easier for Twitter-WhatsApp users. He used the React Builder, Twitter’s tweet search APIs, and guideline-specific Figma-to-code strategies to build the right app in virtually no time.
Here is how Rakesh managed the nitty-gritty of this use case!
Medusa is one of the go-to eCommerce engines out there. However, if you are into manual coding, even using something as intuitive as Medusa for your eCommerce app will take you days. Here is what the problem looks like:
Problem statement: Combining an eCommerce application's front-end (design-specific) and back-end (database-specific) is tedious. Also, if you go the traditional route, the back end needs to be set up first— killing some more time in the process.
Solution: However, Pankti Shah— developer at DhiWise— used the Flutter builder, DhiWise’s Figma-specific code conversion, Medusa APIs, Firebase Authentication, and other resources to build an eCommerce application 75% faster compared to the traditional methods.
Here is how Pankti went about exploring this use case!
Enterprises often need to create survey management apps to get employee and user feedback, arrange competitions, and interact holistically. Yet, building such an application can take days’ worth of effort owing to the following challenges:
Problem statement: There are multiple touchpoints associated: selecting the right survey platform, finding the right messaging service to send across the forms, and even integrating the individual APIs to make the final app most interactive. And yes, even the design needs to be top-notch. Quite a lot to do, right?
Here is how this use case was addressed to perfection!
Interested in working on a quick customer feedback app that saves time, manages work, and prioritizes roadmap over everything else. Here are the standard roadblocks that you might experience:
Problem statement: The app needs to keep customers in the loop, which would need a lot of back-and-forth coding if approached manually.
Solution: However, Ashutosh Dave had a way out. He used DhiWise’s Flutter builder and integrated the same with the Canny APIs (meant for feedback capturing across platforms) to build a functional feedback management application.
Here is how it all went down!
Here is how he approached building the app!
Building an expense management application should be fun! It is, but you must also consider the expenses associated with the design and development cycles. Here is a problem statement to keep in mind:
Problem statement: For building an expense management application, you need the screens to navigate seamlessly to the desired places. You also need to code everything from scratch without a dedicated builder.
Solution: Pankti Shah used the Flutter builder to speed up app development. Pankti even paired the same with Chargebee APIs to make the app more interactive and cover every expense-specific attribute.
Here is how things happened behind the scenes!
Another DhiWise use-case would be to create a payment management application whilst cutting down on the development time and effort. But the catch remains:
Problem statement: Pairing the right payment handling APIs is important. Plus, you need to code extensively for adding navigations, subscriptions based on access, and interactive user experiences.
Solution: DhiWise Flutter builder plus Razorpay APIs were used to build a production-ready mobile application in no time. Zaiynab Mansuri was the brain behind this product, where the older flexibilities of the Razorpay app were looked at.
Here is how the process looked in real time!
As a developer, getting hold of the right version management application is imperative. What if there was a quick way to develop the same? But you need to watch out for a few problems:
Problem statement: Finding the right system for version management and control can be tricky. Plus, you need to prepare the app structure with extensive coding and read through the version manager’s API documentation to understand the same in detail. Seems like a lot of effort!
Here is how the process looks!
GitLab is great as a collaborative tool for development teams. However, it doesn’t have a dedicated mobile app for quick access. But what if we wanted to create one:
Problem statement: Creating a version management app from scratch requires a fun and interactive UI/UX, support against crashes, and mindful API integrations. All of that seems like a lot of work!
Here is how it all went down!
Tracking organization goals, like MBOs and OKRs, require a full-fledged application. Yet, building the same isn’t as easy as it sounds.
Problem statement: Integrating tracking goals within an application requires a lot of time and money. Also, some tracking APIs would be needed to ensure that the application has requests and responses to handle.
Here is what the process looked like!
If you have ever used a CRM platform, you would know how good HubSpot is. However, developing a usable HubSpot mobile app isn’t an easy process, courtesy of the following problems:
Problem statement: A lot of time and effort would be required. Plus, if you want to code from scratch, designing and importing the designs becomes equally tedious. And yes, you would need to go separately about Android and iOS development.
Here is how he went about the job!
Mixapnel— a highly intuitive product analytics platform— doesn’t have a mobile presence. Therefore, using the APIs to develop a Mixpanel application would be a good idea. But certain issues remain!
Problem statement: The trick is to create a MixPanel account, get APIs, plan the app interface, and even account for navigations. All of that sounds like a lot of work, indeed!
Here is how he went about handling this use case!
As a developer, how useful would it be to check the forked GitHub repositories on your mobile? But it might not be as seamless as you plan it to be.
Problem statement: Having an app showing forked responses and code changes requires a clear interface and API integrations. All of that sounds time-intensive, right?
Solution: Subham Jasani— developer at DhiWise— made sure that the app development process is fast and dependable as he used GitHub APIs with the Flutter builder to get things up and to run in virtually no time.
Here is how the entire approach looked:
If you have been an active blogger, you would know the value of one interface for reading and even posting daily articles. Imagine a single blogging platform to find, post, and read blogs across diverse platforms.
Problem statement: Building such an app requires a lot of manual coding, extensive designing, manual design to code conversions, and locating the right APIs.
Solution: Yash Pancholi— developer at DhiWise— developed a blogging app named WeBlog in no time— using Dev.to and Medium APIs, quick Figma imports, and only some manual coding for addressing specific UI changes.
Here is how it all happened!
A good market application is a combination of CRM and user feedback tools. However, developing such an app can have its share of issues:
Problem statement: Getting a user-friendly UI to handle multiple hops and combining multi-platform APIs can sometimes get tricky.
Here is how she went about the task!
As a developer, you would always prefer an app version of the Stack Overflow to get all your questions addressed. But building such weban app might be tricky:
Problem statement: Finding the API and building a minimal yet interactive UI/UX isn’t the easiest task around.
Here is what the process looked like:
Sentry is pretty good for crash-reporting specific product deployment actions as a platform. It is a must for product teams as it lets people in on the deployment cycle. But even Sentry deserves an upgrade.
Problem statement: Sentry— the platform— missed out on the ability to export logs. However, adding a new feature to a third-party app didn’t look doable.
Solution: Jemee Tala used the expertise and action sets pertaining to the React builder to add the export functionality to Sentry. Sentry APIs were used, and even Clickup APIs were used for integration, as exporting reports always requires a mediating interface.
Business processes need to be resolved quickly. Hence, it makes sense to create an application that has answers to all your business problems, like managing orders, handling business needs, and more.
Problem statement: Developing such an app requires multivariate API deployment. Plus, UI/UX planning requires time. Also, the navigations need to be smooth and clear.
Here is how the process happened in the first place!
As a developer, you would want to move beyond a template and build something interactive to show your portfolio to an employer. However, building something like an app can get tricky:
Problem statement: The process needs to be very detailed. All the right APIs need to be integrated. And finally, the UI/UX needs to be minimal and consistent.
Solution: Saloni Saraiya used the React builder and integrated the same with Prisma for the database, Nestjs for the backend, and Figma-to-react for designers. This helped develop the right platform in the least possible time.
Here is what the development process looked like:
Looking to learn to code and prepare for an interview with HackerRank. You can now get it as an app on your mobile phone.
Problem: HackerRank APIs are available, but the design process takes a lot of time. You would also need to code manually to add authentication and navigations.
Here is what the development cycle looked like:
As a product owner, you might have had the pleasure of using ProductHunt for inspiration! What if there was a way to improve the ProductHunt API using DhiWise?
Problem statement: ProductHunt already has a good UI. However, the experience can get a bit overwhelming for new users.
Here is how he went about the process!
If you are a cloud computing evangelist, you would have come across Terraform— a tool that offers Infrastructure as Code. However, what if Terraform— which loads as a browser— can be made more functional as a smartphone application?
Problem statement: The process would require some intuitive design elements. The navigation will need to be seamless, and the business logic will have to be clear.
SAP is a powerful enterprise resource planning tool to help businesses easily handle data processing. However, there is a way to make SAP even more personalized.
Problem statement: Adding custom capabilities to SAP requires intuitive API integrations. Plus, any such app would need to accommodate the right design and business logic.
Solution: Jemee Tala deployed the React builder, Figma support, built-in actions, and SAP APIs to come up with a more personalized version of the APIs.
And that’s a wrap. It took time, but we managed to show how useful DhiWise can be when it comes to building custom business and personal resources. We urge you to go through these use cases, deployments, and exhibits in detail while trying to develop your own versions.
Happy building, folks!