Do you actually need an app or just a better mobile website?

The first email lands late in the afternoon: “Can we get a quick call about our new app idea?” By the time you’re reading the brief, there’s already excitement — a few screenshots, a hasty list of features, someone’s cousin who “knows React Native.” But as soon as you ask, “Why an app and not a mobile site?” the room gets quiet. Sometimes there’s a long pause. Sometimes there’s a little shrug.

We’ve seen this play out more times than we can count. The business is convinced that an app is the next logical step. Their competitors have one. Their customers are “mobile-first.” But a few questions deeper, and the core need is almost always something else: better mobile usability, a faster way to update content, maybe a way to send notifications. The pattern is almost always the same — the solution is decided before the problem is properly understood.

If you’re weighing app vs website for your business, here’s what actually matters — and what most businesses miss when emotions run high and roadmaps start to blur.

The Most Common App Request: Solving the Wrong Problem

In our experience with over 100 digital projects, it’s rare that a business’s first idea is the right one. The most common scenario? A team comes in convinced they need a native app. They describe frustrations — slow site, clunky checkout, poor engagement — and assume a mobile app will fix it.

But nine times out of ten, the real issue is the mobile website itself. It’s not responsive, or it loads like it’s stuck in 2012. The navigation is buried. Images take forever. All of this gets blamed on “not having an app.” In reality, a bad mobile site will haunt your app too. If you haven’t nailed the basics, building an app is like buying new tires for a car with a broken engine.

We’ve lost count of the number of times a client has said, “We’ve been live for 6 months and nobody calls.” The app isn’t the problem. The experience is.

What a Native App Actually Gets You

Let’s be brutally honest: most businesses don’t need a native app. There, we said it. Native apps — the ones you download from the App Store or Google Play — are powerful, but they come with real costs. You get:

Access to device hardware (camera, GPS, sensors)
Offline functionality
Push notifications (the real, system-level kind)
Full control over performance and animations

But here’s what most businesses don’t realise: native apps are expensive to build, test, and maintain. Every new OS version can break your features. You’ll need updates, bug fixes, and a developer on speed dial. And unless you have a clear reason to leverage device hardware or true offline use, you’re paying for complexity you might never use.

Mobile-Optimised Website: The Overlooked Powerhouse

What we see across projects is that a high-quality, responsive mobile website can solve 80% of business needs. Fast load times, clean navigation, and a checkout that works on any screen — that’s what actually moves the needle.

Most users don’t care whether they’re in an app or a browser, as long as they get what they need quickly. For businesses in Slovenia and beyond, the single biggest conversion killer is a slow, clumsy mobile site. We’ve rebuilt 30+ online stores and seen traffic and sales jump simply by prioritising mobile UX. No app required.

If you’re not sure where to start, ask yourself: would a better mobile website fix 90% of the complaints you’re hearing? If the answer is yes, don’t build an app. Build a better site.

When a PWA (Progressive Web App) Is the Actual Sweet Spot

Somewhere between an app and a website sits the much-hyped PWA — and for good reason. A PWA is a website that feels like an app: it loads fast, works offline (to an extent), and can send push notifications on Android and some browsers. It can be “installed” on a phone’s home screen, but doesn’t require the App Store circus.

For many businesses, a PWA is the right answer. Why?

You want push notifications, but don’t need every device feature
You need some offline capability (caching, forms, browsing)
You have a limited budget but want an “app-like” experience

We see this play out especially with retail and service businesses. PWAs can deliver most of the benefits of a native app, with a fraction of the maintenance pain. They’re easier to update, work across devices, and skip the app-store approval headache.

A Real-World Example: When Going Native Made Sense

Out of the 20+ mobile apps we’ve built at Dover Digital, only a handful truly needed to be native. One project stands out: a logistics client needed barcode scanning, GPS tracking, and real-time offline data sync — features that demanded tight integration with device hardware. The cost was higher, the testing was rigorous (especially across Android versions), and the maintenance plan is ongoing. But the business case was strong, and the ROI was clear.

For most others, we’ve recommended a PWA or a high-quality mobile site. In retail, for example, clients often ask for an app to send notifications about promotions. Once we show them what a PWA can do — same notifications, instant updates, no app-store drama — the conversation usually shifts: “Wait, we can do all that without launching an app?” Yes, and you’ll save thousands in the process.

The pattern is always the same: if you don’t need deep hardware access or true offline-first workflows, you probably don’t need a native app.

Budget, Maintenance, and the Hidden Costs Nobody Talks About

Here’s what most businesses miss when dreaming up their first app: the work doesn’t end at launch. With every OS update, your app needs testing, sometimes urgent fixes, and regular updates just to keep working. Add in the cost of app-store compliance, privacy updates, and device fragmentation (especially in Android land), and maintenance can easily outpace the initial build cost within a few years.

A mobile-optimised website or PWA, by contrast, is easier to maintain and update. You control deployment. Bugs can be fixed instantly, and you’re not at the mercy of a third-party approval process. At Dover Digital, we’ve seen clients waste tens of thousands on app maintenance that could have been avoided with a simpler, browser-based solution.

The early excitement of “launching our app” fades quickly when the first round of maintenance bills lands. That’s when the real cost of ownership becomes clear.

How to Decide: A Straightforward Framework

So, do you actually need an app — or just a better mobile website? Here’s how we help clients at Dover Digital decide:

Start with your core user need: Is it content, transactions, or device interaction?
List the features you absolutely cannot live without. Be ruthless.
Ask: Would a fast, responsive mobile site solve this? If yes, stop there.
If you need notifications or offline use, explore a PWA next.
Only if you need deep device access, or your business case depends on the app-store presence, go native. Be ready for the long haul.

It’s not glamorous, but it’s honest. And after 100+ clients, it’s the framework that saves the most money, time, and frustration.

The bottom line: Your customers want results, not icons on their home screen. Choose the approach that serves them — and your business — best.

Let’s build something great together!

Ready to take your digital presence to the next level?

Reach out to us at [email protected] and let’s create something remarkable.

Sorodni članki

Most online stores are built for desktop. Your customers shop on their phones.

The support ticket came in at 7:52 AM. Subject line: “Checkout not working (MOBILE)!!!” The owner of a fast-growing Slovenian fashion brand was already on her second coffee, scrolling through last night’s sales. She’d noticed something off—a spike in abandoned carts, all from mobile users. Her phone buzzed again. A WhatsApp message from her cousin: “Hey, I tried to buy those shoes but your site’s payment button is too small! Gave up.” There’s a moment of silence when she realises it’s not just her cousin. It’s hundreds of people, every single day, getting stuck or giving up for reasons she never sees on her desktop screen. This is the moment we get called. Someone’s finally spotted the gap: the online store looks beautiful on a laptop, but on a phone, it’s like trying to thread a needle with ski gloves. The owner is frustrated, but not surprised. She’s heard complaints, but always assumed “responsive” meant “good enough.” Now it’s costing her real money, and the numbers are staring her in the face. Where Most Stores Go Wrong: Desktop-First Thinking Here’s the pattern we’ve seen across more than 30 online stores: the desktop version gets all the love. The homepage banners are huge and lush. The navigation is logical—if you have a mouse. But try the same site on a phone. Menus collapse into tiny hamburger icons tucked in the far corner. Product images take forever to load on slow data. Add-to-cart buttons shrink into a narrow strip, perfect for accidental taps or missed clicks. The irony is, most store owners make their buying decisions on a desktop, in an office. Their customers? Over 65% of sessions (in real analytics, not a random stat) now come from mobile. But those customers are wrestling with clumsy filters, pop-ups that won’t close, and forms that ask for everything short of a blood sample. What’s breaking isn’t just the layout. It’s the entire experience of buying on a phone—one thumb, one screen, one fleeting moment before something more interesting comes along. Thumb Zones and Tap Targets: The Invisible Roadblocks If you’ve ever watched someone shop on their phone, you know the dance: scrolling with a thumb, stretching for distant buttons, squinting at tiny product images. Most online stores are designed in big rectangles, but real mobile users operate in circles—the natural arc of a thumb. Here’s what we see go wrong, over and over: Add-to-cart and checkout buttons are placed just out of easy reach, leading to missed taps. Tap targets (the clickable area) are too small, making it easy to hit the wrong thing or nothing at all. Sticky navigation covers important content or is so thin it’s useless for big thumbs. These aren’t minor annoyances—they’re silent revenue leaks. Every time a user fumbles and fails, that’s a lost sale. Nobody emails support to say, “Your button was 8 pixels too narrow.” They just vanish, often for good. Mobile Checkout: Where Most Abandonment Happens “The client said: ‘We’ve been live for 6 months and nobody calls. But I just tried to check out on my phone, and it’s a disaster.’” That’s always a tough call to get, because by the time the pain is obvious, it’s been happening for weeks or months. Mobile checkout is where the wheels tend to fall off. Here’s what typically breaks: Endless forms with dozens of fields (address, phone, email—sometimes twice). Mandatory account creation before buying—guaranteed drop-off. Payment popups that don’t resize, making the “Pay” button unreachable on smaller screens. In one project, we saw a 40% drop in mobile checkout completion compared to desktop. No technical bug, just a sequence of small UX missteps: a postcode field that was hard to tap, a “Terms and Conditions” checkbox you had to scroll to find, a credit card input that autocorrected numbers (never a good idea). Image Weight and Loading Times: The Silent Conversion Killer A retailer uploads crisp, high-res product shots that look gorgeous on a 27-inch monitor. But on a phone, especially over a slow 4G connection, each image can take several seconds—or never finish loading at all. The result? Users see a spinning wheel instead of that perfect leather bag, and most won’t wait. We’ve seen stores where mobile bounce rates spiked simply because the homepage banner was a 4MB file. Customers in rural areas or on limited data plans abandon the site before even seeing what’s for sale. In our experience, every megabyte over 1MB costs you sales—and image compression is almost always overlooked in the rush to launch. Real-World Fixes: What Actually Works After working on 100+ digital projects, we’ve learned that mobile e-commerce is its own discipline—not just a smaller screen, but a different mindset. For one hospitality client, their online store had a beautiful desktop design, but Dover Digital was brought in after months of dismal mobile conversion rates. Our audit found: Key buttons sitting in “dead zones” unreachable by the average thumb. Font sizes too small for quick scanning. Images not optimised for mobile loading speeds. We rebuilt the mobile UX, prioritising thumb-friendly layouts, larger tap targets, and a mobile-first checkout flow that reduced steps and pre-filled as much information as possible. The result? Abandonment rates dropped, and the owner stopped getting frantic WhatsApps from friends trying to buy on their phones. Mobile-First Design: More Than Just “Responsive” There’s a difference between “responsive” and “mobile-first.” Responsive design adapts your desktop site to fit a phone—it’s a technical solution. Mobile-first design starts with the phone in mind, making every decision for the person holding a device in one hand and a coffee in the other. At Dover Digital, we see the same pattern: stores that launch “responsive” often miss the nuances that drive real mobile sales. If you’re not testing every step of the journey—from home to checkout—on a real phone, you’re leaving money on the table. What It’s Costing You (And How to Spot the

What to prepare before talking to a web agency — so you don't waste the meeting

It’s 10:47 AM and the Teams call is already running late. Ana is staring at her notes, half-proud she even found time to make them, half-worried they’re all wrong. Her boss had said, “Just get us a quote for the new website. How hard can it be?” The agency’s project manager appears on the call, cheerful, asking, “So, what’s the scope?” Ana freezes. Scope? She has a rough list—“better design”, “faster”, “contact form”—but nothing that feels like an answer. The next thirty minutes are a blur of polite nods and not-so-polite confusion. She leaves the meeting with a vague promise of a proposal and a sinking feeling she’s just wasted everyone’s time. If you’ve ever been in Ana’s seat, you’ll know the script. You’re tasked with “finding a web agency”, but nobody tells you what to prepare. You book meetings, you say words like “modern” and “mobile-friendly”, and you hope the agency will magically fill in the blanks. But after working on 100+ digital projects, I can tell you: the first meeting is where most projects go sideways. Not because of bad intentions, but because both sides are guessing. And that’s how you end up with proposals that don’t match what you need—or budgets that explode three months in. Why the Brief is Everything (and Why Most Are Useless) Here’s what we see across projects: the brief you send to the agency is your one shot at getting a useful answer. If it’s vague, you’ll get a vague proposal. If it’s overly detailed but misses the essentials—actual business goals, real user needs—the agency will spend half its time guessing and the other half correcting. We’ve received briefs that are a single sentence (“We need a new website, ASAP”), and others that are 20-page PDFs with wireframes, mood boards, and three-year roadmaps—without a single mention of what the business actually does. Both extremes have the same outcome: after the kickoff call, everyone is still confused. The best briefs aren’t the longest. They’re the ones that answer a handful of practical questions—enough to let an agency give you an honest, tailored proposal. Here’s what actually helps: What’s the problem you’re solving? (“Customers can’t find our products on mobile.”) What does success look like? (“20% more online orders in six months.”) Who will use the website or app? (Be specific—“parents booking appointments”, “wholesalers”, etc.) What are the must-have features? (Not “blog”—but “integrate with our ERP”, “multi-language support”, “appointment booking with calendar sync”.) What’s your real deadline—and why? (Is there an event, a product launch, or just “as soon as possible”?) Questions to Ask Before You Sit Down With an Agency There’s a moment in almost every first meeting where someone says: “Do you have any questions for us?” This is your cue. Agencies can (and should) ask you about your business, your customers, your old site’s headaches. But you need to be ready to ask them things that matter, too. From working with 100+ clients, here are the questions that actually move the conversation forward: How do you approach projects like ours? (Listen for a real process, not buzzwords.) What’s your handover like? (Will you be able to update content yourself, or will you pay for every small change?) Who will I be working with day-to-day? (A project manager, or will you be lost in a ticketing system?) Can I see similar projects you’ve delivered? (If they hesitate, that’s a red flag.) One client put it bluntly on a call: “We’ve been live for 6 months and nobody calls. Where did we go wrong?” The answer, almost always, is in the questions that never got asked at the start. Reading Proposals: What’s Real and What’s Fluff Let’s say you survived the first meeting and the agency sends you a proposal. Most look impressive—lots of pages, fancy diagrams, estimated hours. But here’s what actually matters, and what should set off alarms: Clear deliverables — Not “modern website”, but “custom Shopify store with payment integration and product filtering”. Timeline with real milestones — If the entire project is one 12-week block, expect delays. Look for breakdowns: design, development, feedback, launch. Assumptions and exclusions — If “content provided by client” is buried in fine print, you’ll be scrambling later. Ask what’s not included. Post-launch support — Will the agency disappear after go-live, or do they offer training, bug fixes, and updates? A proposal should make you feel informed, not overwhelmed. If it’s all buzzwords and no clarity, don’t be afraid to push back. (And if the price is suspiciously low, ask which corners are being cut. In web development, you always pay for them later.) What Timelines and Budgets Look Like—For Real Here’s another pattern: clients expect a simple company website to be live in a month, and a fully-featured online store to cost less than a long weekend at the seaside. I get it—nobody wants to overspend. But after 30+ online stores and 20+ mobile apps, here’s what’s realistic for most projects: A small business website (5-10 pages, no integrations): 4-8 weeks from kickoff to launch, assuming content is ready. Budget: €3,000–€6,000. An online store (Shopify, WooCommerce, custom design, payment gateway): 8–14 weeks. Budget: €6,000–€18,000, depending on features and catalogue size. A custom web or mobile app (user accounts, dashboards, integrations): 12–24 weeks. Budget: starts at €18,000 and scales with complexity. There are always exceptions—rush jobs, or projects that get stuck in feedback loops. But if you hear, “Sure, we’ll build your store in two weeks for €1,500”—ask how many corners they’re cutting. The answer is usually “all of them”. A Real Example: When Preparation Saves the Project We once worked with a Slovenian retailer who came prepared—not with a wall of slides, but with three simple documents: a list of business goals, a spreadsheet of products (with messy data, but at least it existed), and a clear timeline driven by a planned marketing push. The project ran smoother than most—not because

We inherited a website with 43 plugins. This is what we found.

“Why is our homepage taking nine seconds to load?” The question echoed through the conference call. I refreshed the site again, watching the spinning loader. The client was frustrated. Frankly, so were we. Their site looked fine on the surface, but under the hood, it was creaking. They’d just switched web agencies, and this was our first day with their WordPress admin. The dashboard alone took ages to open. A quick glance at the plugins tab said it all: 43 active plugins. Some I recognised. Some I’d never seen. Others hadn’t been updated since 2017. The maintenance log was a graveyard of failed auto-updates. It was the digital equivalent of inheriting a house with an attic full of boxes — and absolutely no idea what was inside any of them. The Real Cost of Plugin Overload Most people don’t see the cost of plugin overload until something breaks. If you’ve ever wondered why your WordPress maintenance bills keep creeping up, or why your site feels slower every month, this is usually where the trouble starts. Each plugin adds its own code, loads its own scripts, and makes your site heavier and more complex. What we see, across 100+ client projects, is a pattern: plugin bloat creeps in quietly. A booking tool here, an abandoned Instagram feed there, a slider for a promotion that ran three years ago. Each one feels harmless. Together, they turn your website into a slow, unpredictable beast. Performance isn’t the only casualty. Every extra plugin is another potential security hole. We’ve seen sites with ten different form plugins, several of which hadn’t received security updates in years. When a vulnerability is discovered, attackers don’t care if you’re a small business — they care that you’re vulnerable. When Maintenance Becomes a Game of Jenga Maintaining a bloated WordPress site is a bit like playing Jenga. Every update is a gamble. Will this plugin update break the others? Which one controls the homepage slider, and why does disabling it crash the contact form? Here’s a quick sample from our audit notes on that 43-plugin site: Four separate caching plugins (all fighting each other, none configured correctly) Two SEO plugins, both adding conflicting meta tags A page builder bundled with 11 “helper” plugins, half of which did nothing but slow things down Old WooCommerce add-ons for payment gateways no longer in use Every update, every tweak, started to feel risky. If you’ve ever had to roll back a site after a “routine” plugin update, you know the feeling. How Plugin Bloat Happens (And Why It’s Hard to Spot) No one sets out to install 43 plugins. It happens gradually, often because there’s no clear ownership of the site. A marketing intern adds a popup tool (“just for the newsletter campaign”), then a developer installs a second gallery plugin for a quick fix. Old agencies leave their footprints. Features get duplicated — but nothing gets removed. The problem is, plugin overload isn’t always obvious from the outside. Your homepage might look fine. But if your site: Takes more than three seconds to load (especially for logged-in users) Regularly breaks after updates Has a “plugins” tab that scrolls for pages — you’re probably overdue for a website cleanup. Cleaning House: The Website Cleanup Process The first step is always an audit. We start by disabling everything non-essential (in a staging environment, never live — trust us). The difference is immediate: load times drop, the admin panel becomes usable, and error logs shrink. In the case of the 43-plugin site, we found that fewer than half were actually needed. Here’s what the cleanup looked like in practice: Merged overlapping functionality (kept one SEO plugin, removed the rest) Deleted anything abandoned by its creator or unused for over a year Replaced heavy plugins with lighter, code-based solutions where possible Moved key features into the theme or custom code to reduce plugin reliance By the end, the site ran on just 14 plugins — all current, all essential. The difference? Page load times dropped from nine seconds to under two. The client’s reaction: “It feels like a new website.” Long-Term Consequences of Ignoring Plugin Overload What tends to go wrong if you skip this cleanup? Here’s what we see most often across the 30+ online stores and 100+ client projects we’ve handled: Slow checkout and abandoned carts — especially painful for e-commerce Security breaches due to abandoned plugins Higher ongoing WordPress maintenance costs (more things to update, more that can go wrong) One client put it bluntly: “We’ve been live for six months and nobody calls.” Turns out, the contact form plugin had been broken for weeks — and the error was buried under a pile of outdated add-ons. When to Call in a Web Agency At a certain point, plugin bloat becomes too tangled to fix internally. This is when clients typically reach out to a web agency in Slovenia like Dover Digital. We’ve seen it all at this stage: sites that won’t update, admin panels that time out, even entire sales flows held together by a dozen interdependent plugins. Cleanup is rarely glamorous, but it’s foundational. By stripping things back, rethinking how features are delivered, and rebuilding the essentials, you get a site that’s faster, safer, and much easier to maintain. And yes — it’s cheaper in the long run. How to Know If Your Site Needs a Cleanup So, how can you tell if your own WordPress site is headed for plugin overload? Here’s a quick reality check: If your “Plugins” list is longer than a screenful, it’s time to review If you’re afraid to update (“just in case it breaks something”), you’re overdue for cleanup If your site feels slower than it did a year ago, start with a plugin audit We handle this kind of website cleanup regularly at Dover Digital. It’s never just about speed — it’s about reliability, security, and being able to actually improve your site without the fear of