Frontend and mobile frameworks · 100% onshore
Frontend and mobile development frameworks, picked for the job
Angular for large business systems. React and Next.js for fast public sites. .NET MAUI for phone apps that keep working with no signal. Our engineers in Irvine, California pick the framework that fits your app, then build it, test it and run it.
Pick the right tool
Five real apps, and the framework we picked for each
There's no best framework, only the best one for a given app. Here's what five of our clients needed, and what we chose because of it.
- Angularlarge business systems with many screens
- React + Next.jsfast public sites and customer portals
- .NET MAUIphone and tablet apps that work offline
- Aurelia + Capacitorone web codebase packaged as phone and TV apps
Quest Industries
ERP for a mold and machining shop- The whole company in one system
- Phones to ultrawide screens
- Light and dark themes
Angular gives a system this big one consistent structure. Quest ERP has 22 feature areas, from quoting to purchasing, all built the same way.
✓Angular (picked)React + Next.js (not picked).NET MAUI (not picked)Aurelia + Capacitor (not picked)Sell Your Boards
Scrap electronics buyback site- 78% of visitors on phones
- Public price list and order form
- Admin dashboard
Next.js and React for a fast, phone-first public site. The code that talks to the back end is generated from the back end itself, so the two never drift apart.
Angular (not picked)✓React + Next.js (picked).NET MAUI (not picked)Aurelia + Capacitor (not picked)Tom's Toolbox
Estimating for a home-improvement franchise- Estimators in homes with no internet
- Sync when back online
- Office website for admins
A .NET MAUI app keeps its own database on the phone and syncs when the connection is back. It was our first MAUI app. The office works in an Angular website.
✓Angular (picked)React + Next.js (not picked)✓.NET MAUI (picked)Aurelia + Capacitor (not picked)American Allied Health
Online school for healthcare careers- Students on Android and iOS
- Student, partner and admin portals
Angular for the web portals and an Aurelia-based app for Android and iOS, both on one back end. Delivered in 7 months.
✓Angular (picked)React + Next.js (not picked).NET MAUI (not picked)✓Aurelia + Capacitor (picked)Artcast
Streaming art on TV screens- Many TV platforms
- A social app for phones
- Admin for the art library
One hybrid app, built in Aurelia and packaged with Capacitor, plays on many TV platforms, with a separate app for Roku. An Angular admin app manages the art.
✓Angular (picked)React + Next.js (not picked).NET MAUI (not picked)✓Aurelia + Capacitor (picked)
lines of TypeScript and HTML, roughly, in Quest ERP's Angular front end
front-end tests, roughly, run on every push to Quest ERP
of Sell Your Boards visitors on phones, so every screen was designed for phones first
TV platforms Artcast's apps play on: Apple TV, Roku, Samsung and Amazon Fire TV
Frameworks as used in each client's project.
How we decide
How we choose frontend and mobile development frameworks
The same questions come first on every project. The answers pick the framework, not habit or hype.
- 01who
Who uses it, and where
At a desk, on a phone, on the shop floor, on a TV screen. The device and the setting narrow the choices fast.
- 02offline
What happens with no signal
If people work where the connection drops, the app has to keep working and sync later, like Tom's Toolbox's estimating app or MedData's iPad app.
- 03shape
Public site or business system
Public pages that must load fast on phones suit Next.js and React. Large internal systems with many screens suit Angular's structure.
- 04platforms
One codebase or native
To reach iOS, Android and more at once, a shared codebase (.NET MAUI, Flutter, or a web app packaged with Capacitor) saves time. When an app needs everything the phone can do, we build natively in Swift for iOS and Kotlin for Android.
- 05prototype
See it before we commit
We prototype the screens first. Sell Your Boards saw a rough prototype before our first call.
- 06we run it
Build, test and run it
Automated tests on every change, releases through a pipeline, error tracking in Sentry and uptime monitoring. We host and manage many of the apps we build.
Frameworks We BuildWith
What each one is good for, and real projects where we've used it.
Angular
Large business systems
Best for: Systems with many screens and many users, where one consistent structure keeps them easy to change for years.
Where we used it: Quest Industries' ERP, American Allied Health's portals, Petra Medical College's three portals, RealSource's Pulse map and Pacific Southwest Container's plant apps.
What it gave them: Quest ERP works on phones and tablets on the shop floor and on ultrawide screens in the office, in light or dark mode.
React and Next.js
Fast public sites and portals
Best for: Public pages that must load fast on phones, with a logged-in portal behind them.
Where we used it: Sell Your Boards: public site, price list, order form, customer portal and admin dashboard, on Next.js 15 and React 19. This website runs on Next.js too.
What it gave them: 47 orders and $4,171.11 paid out to sellers in the first week on the new site.
.NET MAUI
Phone apps that work offline
Best for: Field apps that must keep working with no internet and sync when the connection comes back.
Where we used it: Tom's Toolbox: estimators build job proposals in customers' homes on a cross-platform app that stores them on the device, with invoicing handled through QuickBooks.
What it gave them: Estimating never stops for a bad signal. Everything syncs to the office once the phone reconnects.
Aurelia and Capacitor
One codebase, many screens
Best for: Reaching phones, tablets and TVs from one web codebase.
Where we used it: Artcast's streaming art apps, one hybrid app for many TV platforms plus a separate Roku app, and Carszy's social and safety app for drivers.
What it gave them: Artcast's library of more than 100,000 paintings, photos and videos, in over 900 galleries, is seen in more than 150 countries.
Browser apps that work offline
No app store needed
Best for: Tablets used in places where the internet can't be trusted.
Where we used it: MedData: an iPad app that loads completely in the browser, data and all, so hospital staff can screen patients for coverage programs in all 50 states.
What it gave them: Revenue up 10% to 35% for MedData's clients.
Native iOS, Android and Flutter
When an app needs the whole phone
Best for: Apps that need the best performance and every feature of the device.
How we decide: We build natively in Swift for iOS and Kotlin for Android when that pays off, and use Flutter or .NET MAUI when one codebase for both platforms is the better deal.
What you get: A straight answer on which route costs less over the life of the app.
From a client
American Allied Health had tried other development firms before us. We built their web portals in Angular and their app for Android and iOS, all on one back end.
The code and systems were cutting-edge, and we got incredible documentation for everything along the way.
Not sure which framework fits your app?
Tell us who will use it and where. We'll recommend a framework, explain why in plain English, and tell you what it would take to build.
Talk to an architectCompany Facts
& Figures
Our Office
Get in Touch
Software is what you depend on to get things done. Baytech is who you depend on for software.
