Mobile & Desktop
Native desktop performance improvements
A faster desktop shell that starts quicker and uses less memory so it holds up through a full day of dispatch.
Overview
Operators keep the app open all day, and a sluggish, memory-hungry shell drags down everyone who lives in it. Thorbis is improving native desktop performance with faster startup and a lighter memory footprint. The result you'll feel is a shell that stays responsive from the first call of the morning to the last job of the night.
What we're building
Operators and dispatchers keep the app open from the first call of the morning to the last job at night, so a shell that is slow to start and heavy on memory drags down everyone who lives in it. By mid-afternoon a sluggish app means missed calls and slower dispatch.
Thorbis is improving native desktop performance with faster startup and a lighter memory footprint, so the shell stays responsive through a full day of high-volume dispatch. The result you feel is an app that holds up across long shifts without needing a restart to stay quick. It is built for the people who run dispatch all day and can't afford the tool to bog down when it is busiest.
What you'll be able to do
- Start the desktop shell faster
- Use less memory during all-day sessions
- Keep the UI responsive under heavy use
- Reduce slowdowns for high-volume dispatchers
- Hold up across long shifts without restarts
- Run smoother on lower-spec office machines
- Keep dispatch responsive during peak call volume
Rollout plan
- 01
Faster startup
In progressCut the time the desktop shell takes to launch and become usable.
- 02
Lighter footprint
In progressReduce memory use so the shell stays light through all-day sessions.
- 03
Sustained responsiveness
In progressHold the UI responsive under heavy, high-volume dispatch without needing restarts.
Milestones
- Not started:
Startup profiling
Measure and reduce desktop shell startup time.
- Not started:
Memory reduction
Lower memory use during long sessions.
- Not started:
Load testing
Verify responsiveness under heavy dispatch use.
- Not started:
Stability over shifts
Confirm the shell holds up across full shifts without restarts.
More in Mobile & Desktop
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.