Approach
Pioneer Giant was created to develop solutions in the way we want them: high-performing but well-designed. That's the standard we build to. We also support the majority of platforms, giving the flexibility many of us need.
Interfaces must be natural and simple to use, from the first time, to the hundredth. We put a lot of effort into the small details, from simple things like placing every panel, every button in the right place to remembering your settings and preferences so that you don't have to re-configure it every time. It seems excessive, but these little things count big time.
Most apps are designed around their demo. We'd rather start from what actually needs to be accomplished and what users are looking for, then shape the solution around that: fewer steps, fewer dialogs, and a focus on the outcome instead of the tool.
Bloated software is becoming the standard, just not ours. We care about performance across the board, and about how an app behaves in real use, not just in testing.
No amount of good documentation makes up for needing a full walkthrough just to install an app. We would rather spend that time getting the defaults right, so you are up and running right away.
A feature can convince someone to try an app, but the details determine whether they keep using it. Does it work as intended? Does it freeze or crash? These are not features, they are expectations. We treat them as part of the product, bringing a solid experience in every app we release.
Studio
There is no committee to convince before an idea can make it into production. Our operating model means that going from the right idea to a shipped product is frictionless.
We develop native apps when that is the right call, and reach for cross-platform frameworks when they let us serve more people without the result feeling borrowed. Each decision is analyzed per product, not settled by a house rule.
We do not announce our software in advance, and that is by design. Naming, describing, and pricing an application before the right time becomes a distraction. We would rather spend that time getting it right than deliver it before it is production ready and hand our users a half-baked solution.