When it comes to ideas, clients are the superstars. There’s no limit to what they’ll bring to the table. They know exactly what they want.
But it’s our job to parse it out, distill, and determine what our clients need. It may be a tired old saying, but when it comes to how we work, less is more. And in building less and separating the needs from the wants, not only do we get the job done on your timeline, we find that in the end, you get far more than you could have imagined. By focusing on the highest impact / quickest to complete feature set, we’re able to pass on the greatest return on investment to you.
How We Architect Solutions
Our solutions are built on a core principle of simplicity. It’s a philosophy we call minimal viable product. Essentially, when it comes to writing code our edict is lean and mean. We write the least amount of code necessary, while leveraging everything an existing API has to offer.
These APIs are tried and true, so there is simply no need to waste time and money reinventing the wheel. We build only what the app can’t do, giving you the functionality you want. By building a slim codebase, there’s no overlap in functionality, no waste. The integration is intelligent and clean from the outset.
In our experience, we’ve found that many developers do in fact use APIs, but they tend to use them only for what they are best known for. A perfect example of this is Stripe. When it comes to processing transactions, Stripe is the Holy Grail. But what happens is that developers use it only for processing transactions, yet its capabilities and potential far exceed this one function. Our philosophy is to tap into everything it has to offer.
For instance, Stripe can store users and add user data into the Stripe database as metadata, so why not integrate this fully into your entire website? Then it’s necessary to only build around the integration, resulting in a more specific and tailored user experience.
Stripe has many more benefits that are frequently underutilized or simply overlooked completely, such as:
Ability to add one-time or recurring subscriptions or products
Sell services or products
Manage payment records
Ecommerce technology and platforms are already out there, waiting and full of potential. Stripe is just one example of a very robust API that is already built to integrate beautifully with your site. Using our minimalist approach, you get everything an API has to offer, and we need only build two or three things. It’s all integrated and humming along in sync.
Future-Proof Your Site
Another huge bonus of ecommerce technology is that it’s quick and easy to update with new innovations. For instance, Stripe currently does not accept Bitcoin, but there are plans to add cryptocurrency payment methods.
The benefit here is that it future-proofs your site. Having an API like Stripe fully integrated into your online presence gives it the adaptability needed to capitalize on any technological updates the moment they happen. As soon as cryptocurrency functionality launches, your site will be immediately current and operating on a whole new level. Your site isn’t just built to last, it’s built for the future.
By focusing on ecommerce blocks and passwordless login, the checkout process becomes one of seamless elegance that enables any payment method that Stripe checkout supports or will support in the future.
If there’s one thing we’ve learned from stepping back and observing what and how we build, it’s that people want more. They want what’s next, the latest and most current. It’s probably just human nature, but we’ve found that most people want to see additions, not reductions.
When you build less, you get to iterate, improve, and add. Build too much and you’re in the position of potentially having to remove and take away. Keep the code lean and the end product will be an ongoing process of realizing what clients want. They get to see additions and experience improvements continuously, so they’ll always get the very best version of their site.
Once the initial build is complete, then we can learn from it and see how users interact with it. At this stage it becomes clear what is truly needed, for both clients and our internal team. The need to remove features due to lack of use is reduced significantly.
It’s also at this stage when we typically see a shift in perspective. Clients are able to actually experience how well their site works without all the things they thought they wanted originally. Economize the code build, maximize customer satisfaction, and ultimately the needs become exactly what our customers wanted all along.