View Only
  • 1.  Using Quickbase solely as a backend (Custom Frontend)

    Posted 01-02-2022 16:54


    I was wondering if its feasible to leverage quickbase solely as a backend (to design workflows and data models etc) and connect that to a completely custom user facing application that we're building in React/Next.JS. 

    My use case is so build a tailored project management application for industry specific vertical (home renovation).

    There are two user types each with their own dashboard.

    • Consumers/Homeowners  - they have will have basic dashboard that shows progress of their project, let them upload files or send messages etc (which would need to post to quickbase). 
    • Staff/Designers/Contractors - they would have a dashboard that lets them manage the projects, upload tasks for internal folks to do, send updates to the clients etc. 

    The nature of the project requires that we build completely custom ux for both user types above - the only ones that would be using quickbase would be our software team and workflow designers. Not the core end users. 

    Let me know thoughts and if this makes sense! Thanks in advance.


  • 2.  RE: Using Quickbase solely as a backend (Custom Frontend)

    Posted 07-28-2022 04:03
    I'm also really keen to understand this. I've been looking at bubble io, but just love QB so much that I'm going there's a fully customizable front end.

    Matt Stephens

  • 3.  RE: Using Quickbase solely as a backend (Custom Frontend)

    Posted 07-28-2022 10:37
    We use half and half.. we have developed several external apps which use the API because we wanted custom front ends. I don't see why you couldn't go 100% external.

    Pete James