Build note · One login Free toolsBlogCompany Book a demo

Build note By John Stephens. First published on the Everything Windows and Doors blog ↗

Architecture

One login, three apps.

Each app is good at one job on purpose. That raises a question: who decides who gets into which one?

In development, not shipped yet

Retrostack builds three apps: Aperture™ for the field, Eyewall™ for floor plans and takeoffs, and Quote Converter Pro™ for pricing.

Specialized apps need one front door

A sales rep needs Aperture™ and Eyewall™, and maybe Quote Converter Pro™. A quoter needs Eyewall™ and Quote Converter Pro™, and maybe Aperture™. Some people do everything.

If each app keeps its own user list, the owner manages three lists of the same people. Somebody who left in March still has a login in one of them in June.

So the stack gets one company directory and one sign-in. Being allowed into one app doesn't mean you're allowed into the others. The owner switches each one on per person.

The shape of the stack

  • One loginOne directory and one sign-in for the whole company.
  • Three appsCapture, plan and quote, each built for its own job.
  • One jobThe same job travels from app to app.
  • One owner viewA protected control center for owners and admins: who uses what, and where work is stuck.

What it is not

It isn't a CRM, and it doesn't move jobs through pipeline stages. Aperture™ was built on the rule that field capture never drifts into CRM territory, and that rule holds for the whole stack.

The longer version is on the EWD blog.

Read the original on the EWD blog →