1 Fatal mistake that made an entrepreneur scrap his dream QuickBooks App. Learn this before you start your App!

Building an application that connects with the QuickBooks Online API is a significant achievement for any development team, particularly in the accounting sector. However, gaining acceptance into the QuickBooks App Store requires adherence to stringent technical and security standards. This blog post details my experience consulting a client whose application faced rejection due to non-compliance issues and how we navigated these challenges to achieve compliance.

Client’s initial approach: No-code platform

The client initially chose to leverage a no-code/low-code platform to expedite their application’s design, development, and deployment. This approach offered numerous benefits, including:

• Faster time-to-market
• Reduced development costs

However, the reliance on a third-party platform also introduced significant limitations, particularly in terms of control and compliance.

Challenges Faced: QuickBooks App Store Rejection

Despite the successful connection to the QuickBooks Online API, the App Store rejected the application. The root cause of this rejection was the application’s dependency on a no-code platform that did not meet App Store’s technical requirements for apps and security requirements guidelines. As a separate company managed the no-code platform, the client had no control over its adherence to these critical standards.

Key issues included:

• The no-code platform’s architecture and infrastructure did not comply with QuickBooks’ stringent requirements.
• Limited ability to address security loopholes identified in the QuickBooks security review.
• Lack of support from the no-code platform’s SaaS provider for necessary changes.

Consulting process: Ensuring security compliance and technical standards

Upon engaging with the client, my first steps were to:

1. Understand the key problem the app was intended to solve for QuickBooks users.
2. Review the 45-page security testing report shared by QuickBooks, confirming the validity of the identified security loopholes and remedies.

Challenges during this process included:

• Lack of support from the SaaS company managing the no-code platform, as the client was just another subscriber.
• Realization that the client needed to transition parts of the application to a new platform to ensure compliance.

Fortunately, the client had a fully functional UX and interface based on the no-code platform, making the recreation of the same app a relatively straightforward task.

Outcome and lessons learned: Custom App development for QuickBooks

After a few months of effort, the transition to a custom-built application was successful, allowing the client’s application to meet QuickBooks’ stringent standards. This experience highlighted several key lessons:

• Long-term Compliance: Consider compliance requirements during the early stages of development to avoid costly rework later.
• Control Over Technical Stack: Ensure control over the technical stack to facilitate adherence to necessary guidelines.
• Value of Custom Development: Custom-built applications offer greater flexibility and control compared to no-code/low-code platforms, especially when dealing with stringent compliance requirements.

Conclusion: QuickBooks App compliance

As we know, balancing rapid development with compliance can be challenging but is crucial for long-term success. By transitioning to a more controllable custom QuickBooks app development and ensuring adherence to QuickBooks’ standards, the client overcame the initial rejection and moved forward confidently.

Our Satva solutions journey offers valuable lessons for other developers and businesses aiming to achieve similar goals:

• Prioritize compliance and control in your development process.
• Be prepared to invest in custom development if necessary to meet critical standards.
• Leverage the initial design and UX work to streamline the transition to a custom solution.

Ensuring your app meets all technical and security guidelines from the outset can save significant time and resources, ultimately paving the way for successful deployment and acceptance in the QuickBooks App Store.

FAQs

Q1: Why was the client’s QuickBooks app rejected?

The app was rejected because it was built on a no-code platform that did not meet Intuite’s technical and security standards. The client had no control over the platform’s compliance with these guidelines.

Q2: What were the main issues with using a no-code platform?

The primary issues included a lack of control over the technical stack, an inability to address security loopholes, and limited support from the no-code platform’s SaaS provider for making necessary changes.

Q3: How did the client address the compliance issues?

The client transitioned parts of the application to a custom-built platform where they could have full control and ensure compliance with QuickBooks’ stringent standards.

Q4: What lessons can be learned from this case study?

Key lessons include considering compliance from the start, maintaining control over the technical stack, and being prepared to invest in custom development to meet critical standards.

Q5: What are the benefits of custom QuickBooks Web app development for QuickBooks App Store?

Custom QuickBooks app development offers greater flexibility, control over compliance, and the ability to meet specific technical and security requirements essential for acceptance into the QuickBooks App Store.

More FAQs: [New App assessment and complianc](https://help.developer.intuit.com/s/article/New-app-assessment-process-FAQ) from Intuit developer

Further Reading: Ultimate Guide to QuickBooks Integration for Seamless Financial Management

In Nutshell 

If you’re facing similar challenges with QuickBooks app development or have experienced app rejection, contact us today to learn how QuickBooks Custom app development can help you meet compliance requirements and achieve long-term success.