Web and App Development Technologies

sociallybold / technologies.ts
Build / Technologies

The web and app development technologies we build with.

One list of every language, framework and platform we work in, what each one is good for, and when it is the wrong choice.

◉Front-end, back-end, mobile, CMS, ecommerce, cloud and AI
◉Serving Jacksonville, Ponte Vedra, St. Augustine & Northeast Florida
/** * Technologies * Pick the tool to fit the job, not the other way round. */
How to read this

A map of the stack, not a list of buzzwords.

This page indexes the technologies we build in, grouped the way a project gets decided: the interface, the back end, mobile, the content or store platform, the infrastructure, and the AI layer on top. Every item links to a page saying what it is for and when something else would serve you better.

Some of these we build with every week. Others we mainly inherit and maintain, or advise on before anyone commits, and those pages say so rather than dressing a capability up as a track record. If you just want a recommendation, skip to how we choose a stack.

How we decide

How we choose a stack for a project.

We do not start from a favorite technology. We start from four questions, answer them with you, and explain the trade-off rather than presenting one option as the only one.

✓

What does it have to do?

A content site, a store, a live dashboard and a field app are four different problems. The hardest requirement usually settles it: offline use, hardware access, strict permissions.

✓

What already runs in your business?

If staff sign in with Microsoft 365 and your data sits in SQL Server, a Microsoft-stack answer removes work rather than adding it.

✓

Who maintains it after launch?

We pick technologies with deep hiring pools and long support windows, so you never depend on one developer who knows the trick.

✓

What is the smallest honest version?

Often the answer is less: a progressive web app instead of two native builds, or an integration instead of a replacement system.

✓

What we write down

A short record of the choice, the alternatives and the reason, so it survives staff changes on either side.

✓

What we will not do

Recommend a platform because it is new, or because it suits us to build. The Sitecore, Xamarin, blockchain and IoT pages show where those are the wrong fit.

Proof

Rated 5.0 on Google from 33 reviews.

10+ years in business and 100+ websites and apps launched across the technologies on this page. Rated 5.0 on Google from 33 reviews. Our own site scores in the 90s on Google’s mobile PageSpeed test, which is the standard we build to.

Common questions

FAQ

How do you choose which technology to use for my project?

We work through four things with you: what the system has to do, what already runs in your business, who maintains it after launch, and what the smallest honest version looks like. The hardest requirement usually decides it, and we write the reasoning down.

Do I need to pick a technology before I contact you?

No. Most clients describe the problem rather than the stack, and that is the better way round. If you have inherited a preference from a previous developer, tell us and we will say plainly whether it fits.

What if our existing system is built in one of these technologies?

That is common, and much of this work is inherited rather than chosen. We can maintain what you have, modernize it in stages, or plan a migration when a platform is genuinely at the end of its life.

Do you only work in the technologies listed on this page?

These are the ones we build with regularly or support for existing clients. If something not listed would serve you better, we will say so rather than stretch to cover it.

How do you keep a technology choice from becoming a problem later?

By staying on supported versions, documenting decisions, keeping dependencies current instead of letting them pile up, and testing the paths that matter on every release. That is what makes a future upgrade routine rather than a rebuild.

$ ready_when_you_are()

Tell us the problem. We’ll tell you what to build it in.