Learning Centre

How Do I Get My Team to Support My App Vision?

Simon Lee — Tue, 20 Jan 2026 09:00:00 GMT

Getting a team to support your app vision requires more than just a great idea, it needs alignment across different departments, clear communication about what you're trying to achieve, and the ability to speak to people in terms they actually care about. Over the years of building apps for clients across healthcare, fintech and retail, the biggest roadblock has never been the technology itself... it's been getting everyone in the same organisation pulling in the same direction, and understanding why this particular app matters to the business right now.

How Do I Fix Bugs When There's Nobody Else to Ask?

Simon Lee — Mon, 19 Jan 2026 09:00:00 GMT

Working as a solo developer means you'll spend a lot of time fixing problems that nobody else can see, and the fact is that learning to solve bugs on your own is less about having a perfect method and more about building up a kind of mental toolkit that works when there's nobody sitting next to you who can help. I've been building mobile apps for ten years now, and I can tell you that some of my worst Wednesday afternoon debugging sessions have taught me more than any formal training ever did, because when you're alone with a broken app and a deadline approaching, you learn to think differently about problems and their solutions.

How Do I Design Apps for Elderly People?

Simon Lee — Mon, 19 Jan 2026 09:00:00 GMT

By 2030, one in six people worldwide will be aged 60 or older, and right now the fastest growing demographic of smartphone users is people over 65... which makes sense when you think about how many older people rely on their phones to stay connected with family, manage health appointments, and handle their banking without having to leave the house.

How Do I Design Apps for Hotels and Guests?

Simon Lee — Mon, 19 Jan 2026 09:00:00 GMT

When a guest arrives at a hotel after a long journey, do they really want to queue at reception for twenty minutes just to get their room key? After working on hotel apps for properties ranging from small boutique hotels to large chains with hundreds of rooms, I've learned that the answer shapes everything about how we design these applications... and the difference between a helpful app and one that gets deleted after checkout often comes down to understanding what guests actually want versus what hotels think they want to provide.

How Do I Get Employees to Use Our New Business App?

Simon Lee — Mon, 19 Jan 2026 09:00:00 GMT

How much did you spend building that business app sitting unused on your team's phones right now? Getting staff to use a new business app feels different from launching something for customers, and the stakes are just as high when you've invested anywhere from £30k to £200k in development. The fact is that employee app adoption rates hover around 35% after the first month if you don't get the rollout right, which means two-thirds of your workforce goes back to their old ways of working within weeks. After building apps for organisations ranging from healthcare providers with 500 staff to retail chains with teams across 80 locations, I've learned that technical quality matters less than you'd think when it comes to getting people to actually use what you've built for them.

The difference between an app that transforms your business and one that gathers digital dust usually comes down to what happens in the three weeks after launch, not the six months of development that came before it

Most businesses approach this backwards. They build the perfect solution, then wonder why nobody wants to use it.

Understanding Why Employees Resist New Apps

People don't resist change because they're difficult, they resist it because their current way of doing things already works for them. That delivery driver who still uses a paper checklist instead of your shiny new app isn't being stubborn, he's avoiding the risk of something going wrong during his busiest period when he's got 40 drops to complete before 3pm. The warehouse supervisor who keeps her spreadsheet open alongside your inventory app isn't duplicating work for fun, she's protecting herself in case the new system doesn't capture something her manager asks about later. I've watched this play out differently across industries, and the patterns become pretty clear once you've seen enough rollouts fail. Here are the main reasons teams avoid new apps:

They don't trust it won't lose their work or data when connectivity drops
It adds steps to tasks they could do faster the old way
Nobody explained what happens to their old system or records
The app solves a problem managers have, not one they personally face
They're worried about being monitored or measured in new ways

That last point comes up more than businesses expect. A facilities management company we worked with couldn't understand why their maintenance team ignored the new job logging app until someone mentioned it tracked their location and time spent on each task.

Building Business Case Buy-In Before Development

The conversation about adoption needs to happen before you write a single line of code, not after launch when you're panicking about usage numbers. I've sat in enough Wednesday morning steering committee meetings to know that most organisations start with the solution rather than the problem, which means they're building something nobody actually needs in the way it gets delivered. Before investing significant resources, it's crucial to build a compelling case for board approval that addresses both technical requirements and user adoption challenges from the outset.

Run a two-week diary study with your intended users before scoping features. Ask them to log every time they face the problem your app aims to solve, including what workarounds they currently use. This raw data shapes better solutions than any stakeholder workshop.

The business case needs to answer different questions for different groups:

How Do I Connect My App to Our Company Database?

Simon Lee — Mon, 19 Jan 2026 09:00:00 GMT

A major car parts supplier had just launched their mobile app for mechanics to check stock levels and place orders, but three weeks after going live their support team was drowning in complaints... the app showed products that weren't actually available, prices that didn't match the current catalogue, and order confirmations that never appeared in the main system. The problem wasn't the app itself, it was how the app talked to their company database, or rather how it didn't talk to it properly. Getting your mobile app to connect with your existing business systems is one of those things that sounds straightforward until you actually start doing it, and then you realise there are dozens of decisions to make that will affect whether your app becomes a useful tool or an expensive mistake.

How Do I Choose Which Countries to Launch My App In?

Simon Lee — Fri, 16 Jan 2026 09:00:00 GMT

Expanding an app beyond your initial launch country is one of those decisions that looks straightforward on paper but gets complicated fast once you start digging into the details. Most app founders think about international expansion in terms of potential downloads and revenue (which makes sense), but the reality is that choosing the right markets requires you to weigh up dozens of factors that all interact with each other in ways that aren't immediately obvious... and I've seen plenty of projects lose serious money by rushing into markets they didn't properly understand.

How Do I Design Apps for Pet Owners and Vets?

Simon Lee — Fri, 16 Jan 2026 09:00:00 GMT

Pet apps sit at an interesting intersection between healthcare software and consumer lifestyle apps, which means the design approach needs to balance medical accuracy with the emotional bond people have with their animals. Over the years, we've built apps for veterinary clinics, pet insurance companies, and pet care platforms, and the challenges are quite different from standard healthcare applications because you're dealing with non-verbal patients and owners who are often making decisions under stress.

How Do Apps Use Light Detection Technology?

Simon Lee — Wed, 14 Jan 2026 09:00:00 GMT

Have you ever wondered how your phone knows exactly where to place that virtual sofa in your living room or how it can measure the length of a wall just by pointing the camera at it? Light detection technology sits quietly inside millions of phones, doing work that would have seemed like science fiction just a few years back (still feels a bit unreal when I explain it to clients). The sensors in modern phones can now shoot out invisible light beams, measure how long they take to bounce back, and use that information to understand the shape and size of the world around them... something we've been building apps around for the past few years with some pretty interesting results.

How Do I Build My App to Handle Ten Times More Users?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

A pet care booking app launched with two thousand users and worked perfectly, the response times were under a second and nobody complained about slow loading times. Six months later they ran a marketing campaign that brought in twenty thousand new users over a single weekend... and by Monday morning the app was timing out on basic searches, image uploads were failing completely, and their customer support inbox was filling up with angry messages. The company had to temporarily disable new registrations whilst they scrambled to fix their infrastructure, losing potential customers and damaging their reputation in the process.

Planning for growth isn't about predicting exact numbers, it's about building systems that can adapt when success arrives faster than expected.

Most app developers focus on getting their product launched and acquiring those first users, which makes sense because you need to validate your concept before spending money on infrastructure you might not need. The problem comes when you treat scaling as something you'll deal with later rather than designing for it from the start. You don't need to build for a million users on day one, but you do need to understand which parts of your architecture will break first when growth happens, and have a plan for addressing those bottlenecks before they bring your app down. Over the past ten years I've worked with dozens of apps that faced this exact situation, and the ones that handled growth successfully all had certain things in common when it came to how they built their backend systems and planned their infrastructure.

Understanding What Scalability Really Means for Mobile Apps

When people talk about scaling an app they often think it just means handling more users, but that's only part of the picture. Scalability means your app can handle increased load without degrading performance or requiring a complete rebuild of your systems. It means when you go from ten thousand to one hundred thousand users your costs increase proportionally (or less) rather than exponentially, and your team doesn't need to work around the clock just to keep the lights on. There are two types of scaling you need to think about and both matter for different reasons. Vertical scaling means making your existing servers more powerful by adding more memory or faster processors, which is the simpler option but eventually you hit physical limits and costs start climbing fast. Horizontal scaling means adding more servers to distribute the load across multiple machines, which requires more thoughtful architecture from the start but gives you much more room to grow without hitting hard limits. The biggest misconception I see is developers thinking they can just throw more server power at performance problems when they arise. Some problems can't be solved by bigger servers, especially ones related to how your database is structured or how your app makes network calls. A poorly designed database query will still be slow even on a powerful server, and an app that makes fifty separate API calls to load a single screen will struggle regardless of your backend infrastructure. This is one of many aspects worth considering when you're setting realistic growth targets for your mobile app.

Response time staying under 2 seconds even during peak usage periods
Database queries completing in under 500 milliseconds for typical requests
Server CPU usage staying below 70% during normal operation
Memory usage that doesn't continuously grow over time
Error rates staying below 1% of total requests

Building Your Backend Infrastructure to Support Growth

Your backend architecture needs to separate concerns from the beginning, which means breaking your system into distinct services that can scale independently. A monolithic architecture where everything runs in one large application makes it impossible to scale the parts that need it most... if your image processing is slowing down you end up scaling your entire application even though the database queries are running fine. Look at microservices architecture or at minimum a service-oriented approach where you split functionality into separate components. Your authentication service, database layer, media processing, and API endpoints should all be able to scale independently based on where the load actually sits. This doesn't mean you need dozens of separate services from day one, but you should structure your code so that separating components later doesn't require rewriting everything. Understanding these architectural decisions becomes especially important when considering whether to split your app into multiple products as you scale.

Start with a modular monolith that's organised into distinct logical services within a single codebase, then extract the highest-load components into separate services only when you have real usage data showing where the bottlenecks are.

Cloud platforms like AWS, Google Cloud, or Azure give you the tools to scale horizontally without buying physical servers, and they let you use managed services for databases, caching, and file storage that handle much of the scaling complexity for you. The trade-off is you become dependent on their infrastructure and costs can climb quickly if you're not careful about monitoring usage, but for most apps the flexibility is worth it compared to managing your own servers.

How Do Developers Protect Apps During Building?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Developers often worry about app security after launch, but the truth is that some of the worst security breaches happen during the development process itself. I've seen teams who spent six months building a brilliant healthcare app only to discover that their entire codebase, including patient data structures and API credentials, had been exposed on GitHub for four of those months because someone forgot to add the environment file to the gitignore list. The damage was done long before the app ever reached the app stores, and the cost of fixing it was somewhere around £45k in legal fees and security remediation work alone.

How Do I Choose Which Boss Makes App Decisions?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

About 70% of app projects get stuck in what I call decision paralysis, where different people in an organisation think they should be making calls about features, design, or technical direction. This creates a sort of bottleneck that can add months to your timeline, and I've watched this same pattern play out across healthcare apps, fintech platforms, and e-commerce projects over the past ten years of building apps at Glance.

How Do Emotions in App Store Listings Affect Downloads?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

A productivity app with thousands of five-star reviews sits at position seven in the App Store search results, whilst another productivity app with fewer reviews and a lower rating sits at position three and gets downloaded three times more often. The difference comes down to something that most app developers miss when they're putting together their store listings... the emotional triggers in their screenshots, descriptions and preview videos work harder than the features list ever could.

How Do Apps Learn From What You Do?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Have you ever noticed how your favourite music app seems to know exactly what song you want to hear before you even search for it, or how your shopping app somehow remembers that you prefer blue trainers over red ones? The apps on your phone are constantly learning from everything you do, watching your taps and swipes like a very attentive assistant who takes notes about your preferences. Over the past decade building apps for healthcare companies, online shops, and entertainment platforms, I've worked directly with the systems that make this happen, and the truth is that most people have no idea just how much information their apps gather every single day. Apps use something called machine learning, which is a type of computer technology that helps them recognise patterns in your behaviour and make better guesses about what you'll want next. The process happens quietly in the background whilst you browse, shop, watch videos, or chat with friends, collecting tiny pieces of data that build up into a complete picture of your habits and interests.

How Can I Tell If My App Building Platform Is Safe?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Choosing a platform to build your mobile app means trusting that service with your business data, your users' information, and often your entire digital presence. The problem is that many app building platforms look professional on the surface but have serious security weaknesses hidden underneath, and by the time you discover these issues (sometimes through a data breach or service failure), it's often too late to protect yourself or your users without significant cost and disruption.

Can Your App Work When the Internet Goes Down?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Around 60% of mobile users experience network problems or complete connection loss at least once per day, whether they're in a basement car park, on the Underground, or in an area with patchy signal...and this single fact explains why offline functionality has become one of the most requested features in mobile app development. I've built apps for healthcare companies where doctors needed to access patient records in rural areas with spotty coverage, and I've worked on retail applications where sales teams needed to process orders in shopping centres with dead zones, and the pattern is always the same...users expect apps to work regardless of their connection status, which makes sense when you consider that connectivity issues are part of daily mobile usage rather than rare exceptions.

Can I Build a Secure Payment System on My Own?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

More than half of all apps that collect payments will experience some form of payment-related issue in their first six months, from failed transactions to security vulnerabilities that could have been avoided. The question of whether you can build a secure payment system on your own is one I get asked probably once a week, and the answer is both simpler and more complicated than most people expect.

How Do Haptic Feedback Systems Actually Work?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Most users can't tell when haptic feedback is done well, they just know something feels wrong when it's missing or badly implemented. I've watched countless app demos where the visuals were perfect and the functionality worked exactly as intended, but the whole experience felt sort of hollow because the haptic response was either too aggressive, too weak, or completely absent. The truth is that touch feedback has become such a fundamental part of how we interact with our phones that its absence creates this strange disconnect between what users see and what they feel, and that gap can make even the most beautifully designed app feel cheap or unresponsive.

How Can One Person Manage Both iOS and Android Development?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

More than half of solo app developers end up maintaining two entirely separate codebases for iOS and Android, which means they spend twice as long fixing the same bugs and adding the same features on different platforms. I've been building mobile apps for a decade now, working with everyone from small startups to established healthcare providers, and the question I get asked most often is how one person can possibly manage both platforms without going mad. The short answer is that you probably shouldn't try to maintain two native codebases if you're working alone... but there are ways to build for both platforms that won't consume your entire life.

How Can I Stop Data Leaks in My Development Setup?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Over 80% of data breaches in app development happen because of mistakes in the development setup rather than from hackers breaking through firewalls. I've been building mobile apps for a decade now and I've seen this pattern repeat itself more times than I'd like to admit, where a perfectly secure production environment gets compromised because someone left database credentials in a config file or pushed an API key to GitHub by accident. The reality is that most developers focus heavily on securing their live apps but treat their development environments like they're somehow protected by magic... and that's exactly where the problems start. Look, I've worked with teams who spent fifty grand on security audits for their production systems only to discover that their biggest vulnerability was a junior developer's laptop with full production access sitting in a coffee shop on public WiFi. Data leaks during development aren't just about losing customer information either, they can expose your entire business logic, proprietary algorithms, and competitive advantages before your app even launches.

Do You Need a Lawyer Before Submitting Your App?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Have you ever wondered whether clicking submit on your app could land you in legal trouble... and the honest answer is that it depends on what your app actually does. The fact is that some apps can go live without any legal review at all, while others need proper legal guidance before you even start building them (learned that the hard way with a fintech project back in 2016).

Can Your App Launch Without Regulatory Clearance?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

A pet care startup spent nine months building an app that helps dog owners track their pet's medication schedules and health symptoms. The interface looked beautiful, the features worked perfectly, and they had secured meetings with three major veterinary chains who wanted to trial it. Then someone asked if the app needed medical device approval. The launch stopped dead, and the team spent another six months working through regulatory submissions they didn't know existed. They burned through most of their runway before a single customer could use the product.

Do Beta Apps Need to Follow the Same Legal Rules?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Beta testing apps has become a standard part of the development process, but the legal side of pre-release testing catches a lot of people off guard because they assume beta means fewer rules apply. The truth is that beta apps need to follow almost all the same legal rules as fully launched apps, and in some areas the requirements are actually stricter because you're collecting feedback and user data in ways that published apps might not.

Can You Copy Another App's Regulatory Approach?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

The fashion industry learned this lesson the hard way when several clothing rental apps launched across Europe, each assuming they could follow the same regulatory path as their competitors. One app copied the terms and conditions almost word for word from a successful competitor in Germany, only to face enforcement action in France because they had missed the differences in consumer protection laws between the two countries. The thing is, the public-facing compliance documents you can see from other apps only tell part of the story, and copying what appears to work for someone else can lead you straight into legal problems.

What Financial Reports Do I Need to Track App Success?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

App developers often dive into building their product without setting up proper financial tracking, which means they end up making decisions based on gut feeling rather than real numbers. The truth is that tracking app success goes far beyond monitoring downloads or checking your bank balance at the end of the month, you need specific reports that show what's working and what's draining your resources. After building apps for nearly ten years now, I've seen companies with thousands of downloads go bust because they weren't tracking the right numbers, while others with modest user bases thrived because they understood their finances properly. Mobile apps create unique financial challenges that traditional business accounting doesn't always capture well, particularly when you factor in subscription models, platform fees, and the timing gaps between when users download your app and when you actually receive payment.

What Documents Do Investors Need Before Funding My App?

Simon Lee — Tue, 13 Jan 2026 09:00:00 GMT

Getting investor meetings is hard enough, but then you sit down and they start asking for documents you didn't know you needed to prepare. I've watched founders scramble to pull together paperwork while their funding window closes, and it's honestly painful to see because most of this stuff should have been ready weeks before that first pitch meeting. The documentation investors want hasn't really changed that much over the years (they've always wanted to see numbers and proof), but the level of detail they expect has definitely increased, especially when it comes to technical specifics and data protection compliance.

What Do Venture Capitalists Want to See in My App?

Simon Lee — Mon, 12 Jan 2026 11:11:12 GMT

Venture capital funding represents one of the most common ways that mobile apps secure the investment needed to scale from modest user bases to millions of downloads, but the truth is that most app founders approach this process with some pretty big misconceptions about what investors are looking for. After building apps for over a decade and working closely with founders through their funding journeys (some successful, some not so much), I've seen how the gap between what founders think matters and what VCs actually examine can be the deciding factor in whether you walk away with investment or just polite rejection emails.

How Much Money Should I Keep Back for App Marketing?

Simon Lee — Mon, 12 Jan 2026 11:11:10 GMT

A property management company spent eighty-five grand building a tenant portal app that handled everything from maintenance requests to rent payments, the interface was clean and the features worked exactly as promised, but they kept back just three thousand pounds for marketing because they assumed their existing tenants would naturally download it... six months after launch they had a seven percent adoption rate and the app sat largely unused because nobody really knew it existed or understood why they should bother switching from email and phone calls.

How Do I Use My App's Data to Get More Funding?

Simon Lee — Mon, 12 Jan 2026 11:11:04 GMT

A social media scheduling app launched with 50,000 downloads in its first month and the founder thought investors would be queuing up to write cheques. They weren't. The app had decent download numbers but the data told a different story...daily active users sat at just 8%, retention after seven days was below 15%, and most users never scheduled more than two posts before disappearing. The numbers showed that people were curious enough to download but not engaged enough to stay, and that's exactly the kind of red flag that makes investors close their wallets.

How Do I Get Sponsorship Deals to Pay for My App?

Simon Lee — Mon, 12 Jan 2026 11:11:00 GMT

What if you could build your app without emptying your bank account or giving away chunks of equity to investors... by getting brands to pay for the whole thing instead? The fact is that sponsorship deals have funded everything from fitness tracking apps to educational platforms, often covering six-figure development costs whilst letting founders keep complete ownership of their companies. Over the past ten years, we've helped clients secure sponsorship agreements ranging from £15k for small utility apps right through to £250k for more complex platforms, and the approach that works has changed quite a bit as the app market has matured and become more crowded than it was back when simply having an app was newsworthy. The route to getting sponsorship money isn't about sending generic pitch decks to random marketing departments (that almost never works), it's about understanding what sponsors actually need and building your app concept around solving their specific problems whilst genuinely helping your users at the same time.