Blog | Apps with Rob

No articles match your search.

Getting Started

Don't forget to do your homework

Before you hire a designer or spend a dollar, have you actually done the homework on your app idea?

Getting Started

How to validate your app idea before spending a cent

Free, practical ways to find out if your idea has real legs before you invest real money.

Getting Started

How to prepare for your first app design project

You don't need a spec or a technical background. Here's what actually helps before your first call.

Getting Started

The notebook you've been ignoring for seven years

You've had an app idea scribbled in a notebook for years. Here's why that nagging feeling is the strongest signal your idea has real potential.

Getting Started

What if nobody downloads it?

The fear that nobody will use your app is real. Here's what the data says about app failure rates, and what you can do to beat the odds.

Getting Started

When your family thinks you're wasting your money

Your kid thinks it looks outdated. Your partner thinks you're throwing money away. The emotional side of self-funding an app nobody around you fully understands yet.

Getting Started

Why subject matter experts build the best apps

You don't need a tech background. You need ten years in your industry. Here's why that matters more.

What is an MVP and why should your first app be one?

You don't need to build everything at once. Here's why starting small is the smartest move.

A prototype is not an MVP

People use these terms interchangeably, but they're not the same thing. Here's the difference and why it matters.

The difference between a feature and a solution

Everyone comes in with a feature list. Most of it doesn't need to be in version one. Here's how to find the core.

One app or two? iOS, Android, or both

The platform question every first-timer asks. Here's a practical breakdown for the Australian market.

How to name your app without overthinking it

You've spent months on the idea. Now you're stuck on the name. Here's a practical approach informed by App Store optimisation research.

The recording problem nobody warns you about

Recording a doctor's appointment seems obvious. Then you hit legal questions, storage costs, and AI accuracy. The most useful-sounding feature is often the most complicated.

Designing for the person who can't read your app

5.5 million Australians have a disability. If your app isn't designed with accessibility in mind, you're excluding a massive audience.

Why your app shouldn't speak your industry's language

You know your industry's jargon inside out. Your users might not. Here's why plain language isn't dumbing it down — it's making it work.

One app, three users: why permission layers matter

Most apps have more than one type of user. If you don't design permission layers from the start, you'll end up with a mess or a security risk.

Voice reminders changed everything

When we designed voice reminders for an NDIS app, we ran straight into platform limitations. Here's what we learned.

Why we removed the photo upload

Adding features feels like progress. Removing them feels scary. But the best apps aren't the ones with the most features.

The accountability gap

In NDIS, aged care, and community services, the gap between what's promised and what's delivered is often invisible. Better software can close it.

Don't hide things from people who forget things

Dropdowns and collapsible menus are standard UI. But for users who get distracted or can't hold two steps in their head, hidden elements aren't clean design. They're barriers.

Colour isn't decoration. It's how people navigate.

When some of your users can't read, colour becomes more than a brand choice. It becomes the way they understand their week.

The font that changed everything

Most people pick a font because it looks good. For users with reading difficulties, the font is the difference between understanding the screen and staring at shapes.

Big box days and small box days

Standard calendars treat every day the same. Your users don't experience their week that way. Here's how variable-sized boxes turned a calendar into a navigation system.

Why we added a bowel chart to the app

Nobody wants to talk about it. But for people on medication or in care, tracking bowel movements is a medical necessity. Here's how we designed the feature nobody wants to think about.

Auto-save isn't a feature. It's a safety net.

If your user gets a phone call mid-form and comes back ten minutes later, is their data still there? For users who get distracted easily, auto-save is the whole game.

What your support worker sees on day one

A new support worker walks in. They've never met the person. They need the right information immediately and none of the information they shouldn't have.

Why we renamed a feature mid-build

We used the industry-standard term. It was accurate. It was precise. And real users had no idea what it meant.

Never explain yourself twice

Every time someone changes service providers, they start from scratch. New forms, new intake, new everything. Enter it once, share it with whoever needs it. That's dignity.

The real cost of designing and building an app in 2025

A straight breakdown of what it actually costs in Australia and where your money goes.

Why fixed pricing beats hourly rates for app design

Hourly billing creates bad incentives. Fixed pricing puts you and your designer on the same team.

Self-funding your app: what most first-timers get wrong

Most app founders aren't venture-backed. They're using their own savings. Here's how to think about self-funding without losing your shirt.

The R&D Tax Incentive for Australian app builders

If you're building an app in Australia, the R&D Tax Incentive could give you back up to 43.5% of your eligible development costs.

What to look for when hiring an app designer in Australia

Agencies, freelancers, offshore. It's overwhelming. Here's how to pick the right one.

Why I only work with Australian-based development teams

Offshore development is cheaper upfront. But when you factor in rework and miscommunication, the savings often disappear.

Your app's first usability test should embarrass you

You don't need a lab. You need one real person, one task, and the discipline to shut up and watch.

Getting Started

Nobody's going to steal your app idea

You want NDAs before the first meeting. You think someone will hear your concept and beat you to market. They won't. Here's why.

Getting Started

You've been thinking about this for years. That's a problem.

The longer you've sat on your app idea, the harder it is to cut anything from the first release. Your accumulated vision becomes the enemy of a focused MVP.

Why your quote came back double

You expected $60K. The quote says $120K. Here's why development quotes almost always come back higher than expected, and what you can do about it.

When your prototype becomes your pitch deck

Slides don't convince anyone. A clickable prototype on a phone does. Here's how the prototype becomes the most powerful sales tool you'll ever have.

Your app is actually three apps

You described one app. But it has three user types, each needing their own experience. That's not one app. That's three.

Start in one suburb, not the whole country

Your app works everywhere. Great. But launching everywhere means proving it nowhere. Here's why geographic focus matters.

Compliance isn't a feature. It's the architecture.

If your app operates in a regulated industry, compliance shapes every screen, every flow, every data decision. Here's what that means for your budget.

Fewer screens forced better thinking

A client wanted fifty screens. I gave them fifteen. The constraint forced better prioritisation, and the app was better for it.

The default matters more than the option

Your users don't want to customise everything. They want something that works out of the box. Smart defaults beat endless settings screens.

Simplicity is harder to sell than complexity

Clients want more colours, more options, more visual variety. They think it looks more professional. But restraint is the harder, better design choice.

Your developer is not your vendor

Most founders treat the developer relationship like hiring a tradie. Get quotes, pick the cheapest, wait for the job. App development doesn't work like that.

Phase two is not a graveyard

Every feature you cut from your MVP feels like a loss. But phase two isn't where ideas go to die. It's where they wait until you've earned the right to build them.

Send the deck before the meeting

Most design meetings waste half the time on consumption. Send the materials first. Come to the meeting with decisions, not reactions.

Your timeline is wrong. Here's why.

You think you'll have a working app in six weeks. You won't. Here's the reality of app timelines and why design and development are separate phases.

The content bottleneck nobody plans for

Your app needs content before it can be built. Categories, entries, template text. And that content has to come from you. Here's why it catches everyone off guard.

Scope creep starts with "while we're at it"

The four most expensive words in app development. Every "quick addition" adds cost, delays the timeline, and pushes your MVP further from launch.

The update nobody budgets for

Your app launched. Now here come the OS updates, server costs, bug fixes, and security patches. The ongoing costs that catch every first-time founder off guard.

Why the quote doesn't include marketing

You got your design and development quotes. Neither one includes how people will actually find your app. Here's why marketing is a separate budget.

Getting Started

The difference between a designer and a developer

One figures out what to build. The other builds it. Most first-time founders don't know the difference, and that confusion costs them thousands.

Getting Started

You don't need a technical co-founder

You've been told you need a tech person on your team before you can build anything. You don't. Here's why domain expertise matters more than coding ability.

Getting Started

Why your second attempt usually works

Your first try at building an app didn't go well. That failure wasn't wasted. Here's why the second attempt is almost always better.

AI won't design your app for you

AI tools can generate screens and write code faster than ever. But they can't replace the thinking that makes an app actually work for real people.

The App Store won't market your app for you

You built it. You launched it. Now you're waiting for downloads. They're not coming. Here's why the App Store isn't a marketing channel.

Your competitor's app doesn't matter as much as you think

You found a similar app and now you're panicking. Don't. Execution and domain expertise matter more than being first.

What happens between the prototype and the App Store

You've got a prototype on your phone. It feels real. But there's a whole phase between here and a live app that nobody explains upfront.

What happens on the first call

You've booked the call. You're nervous. Here's exactly what happens in the first conversation, what I'll ask you, and what you'll walk away with.

Why I say no to some projects

Not every project is the right fit. Some ideas aren't ready. Some budgets don't match the scope. Here's why saying no is better for both of us.

Your app should know more than your user

Users don't want a blank canvas. They want something that's already 80% done based on what they told you at the start. Pre-populating beats customising every time.

Every word in your app is a design decision

Button labels, menu items, error messages. The words inside your app aren't content. They're design. Microcopy deserves the same attention as layout.

Why your developer built more than I designed

I designed 30 screens. The developer quoted on 40. That's not scope creep. That's a developer who understands what the design needs to actually work.

Your app's real competitor is a group chat

You searched the App Store for competitors. But the thing you're actually replacing isn't another app. It's a WhatsApp group, a shared spreadsheet, or a stack of sticky notes.

When your app name makes a promise

If your app name implies ease or simplicity, every friction point in the UX contradicts the brand. Your name sets an expectation the product has to deliver on.

Copy-paste before you integrate

You want built-in SMS, email, and push notifications from day one. You don't need them. Start with templates people copy and paste. Prove the feature works before you automate it.

Getting Started

The budget that tells you the market is real

A client found a competitor making six figures a year with zero marketing spend. That's not a threat. That's the best market validation you could ask for.

Test first, learn second

Instead of asking users to pick a learning path, give them the test. They fail. The failed sections become their curriculum. No onboarding quiz. No decision paralysis. Just start.

Getting Started

The product people don't know they need

Nobody is googling your app idea. The market exists but the search demand doesn't. Here's how to validate and launch something nobody knows to look for yet.

Your app doesn't expire when the job is done

The user passed the exam. They're done, right? Wrong. Upskilling, certifications, and mandatory refreshers mean the same customer comes back with a bigger wallet.

The visual gap in text-based industries

The training is 99% text. The actual work is 100% visual. When how people learn doesn't match how they work, there's a design opportunity hiding in plain sight.

Getting Started

Your first users are sitting next to you

You don't need a beta program or ads. Your colleagues and professional network are your built-in test audience. Five honest testers beat five hundred strangers.

Why fixed pricing beats subscriptions for niche apps

Subscriptions feel like pressure. Module pricing feels like ownership. For niche apps with a specific goal, fixed pricing converts better and builds more trust.

Learning to study again at 33

Your user hasn't been in a classroom for a decade. Traditional learning doesn't work for them anymore. Designing for adult learners changes everything about your app.

Getting Started

The first meeting is always the hardest

You've never pitched your app idea to a stranger before. The nerves are normal. Here's what that first conversation actually looks like and why it gets easier.

Getting Started

The ideas that keep coming at 2am

Your brain won't stop adding features. Every shower, every drive, every 2am wake-up brings another idea. That creative overflow is normal. Here's how to capture it without derailing your MVP.

Getting Started

Your idea started with a conversation, not a business plan

Most app ideas don't start in a boardroom. They start over a beer, on a job site, or in a text message that landed wrong. That informal origin is a strength, not a weakness.

When your day job pays for your side project

You're not a venture-backed founder. You're funding your app from your day job. FIFO rosters, shift work, and irregular income create unique challenges for app timelines and budgets.

The Slack channel you didn't know you needed

Most of my clients have never used Slack before the project starts. But one shared channel changes how the whole project runs.

The screen budget is real

Every design package has a screen limit. That number isn't arbitrary. It drives your development cost, your timeline, and the decisions you have to make about what gets in.

Why the first version looks grey

You expected colour and polish from day one. Instead you got grey boxes and placeholder text. That's not lazy design. It's the most important stage of the whole process.

The diagram your industry has been missing

Some industries run entirely on text. Manuals, regulations, study guides. When you introduce visual thinking into those spaces, everything changes.

Colour vibration and why your designer said no

You picked two colours you love. Your designer rejected the combination. It's not about taste. It's about what happens when certain colours sit next to each other on a screen.

The number plate that became the brand

The best branding doesn't come from a mood board. It comes from a UX decision that captures something true about your users.

Dark mode is not a style choice

Dark mode looks cool. But for some of your users, especially anyone over 40, it actually makes things harder to read. This is a usability decision, not an aesthetic one.

The product people don't know they're searching for

Nobody's Googling your app idea. The search volume is zero. But that doesn't mean the demand is zero. It means you're building something the market hasn't named yet.

Why your app needs two on-ramps

Some users need the full guided journey. Others want to skip straight to the part they care about. One onboarding flow can't serve both.

The exam your user already failed

Instead of asking users what they want to learn, give them the test. They fail. The failed sections become their curriculum. It's diagnostic-first design and it works beyond education.

Your app solves one problem. Your pitch deck solves another.

Your prototype is for users. Your pitch deck is for investors. Don't confuse the two audiences or you'll end up with a product that impresses nobody.

The partnership that funds your next phase

You don't have to fund every phase yourself. Industry partnerships, API agreements, and tool sponsors can help fund your next stage of development.

Start with the slang

Every industry has its own language. The slang your users already use is free branding. It builds instant credibility and recognition.

The name that boxes you in

A name too specific to your MVP audience could lock you out of your long-term market. Think about where the product goes, not just where it starts.

Your logo is not your brand

You've spent weeks on a logo before designing a single screen. That's backwards. Your brand is the experience people have with your product, not a graphic on your splash screen.

What your designer is actually doing between meetings

You had a meeting on Monday. The next one is Thursday. In between, it feels like nothing's happening. Here's what's actually going on during the silence.

Your developer will charge you for things I didn't design

I design 30 screens. Your developer quotes on 45. That's not a mistake. Loading states, error messages, and edge cases all need to be built.

The Loom video that replaced the meeting

Your schedule doesn't fit neat meeting blocks. A five-minute Loom walkthrough can move the project forward without waiting for a calendar slot.

The report you actually need to read

Early in the project, I send a product report. Clients who read it before the next meeting get dramatically better outcomes. Here's what's in it and why it matters.

Getting Started

What an API actually is and why you care

APIs sound technical but they're simple. Three real client examples explain what they are, why your app probably needs one, and what it means for your budget.

The database decision that saves you later

How you structure your content before development starts can save you thousands later. The database isn't glamorous, but it's the foundation everything else sits on.

Your app needs to work on bad internet

Mine sites, regional towns, and basement offices. Your Australian users don't always have reliable internet. If your app assumes a perfect connection, it will fail the people who need it most.

Subscriptions feel like a leak

Your users don't love subscriptions. They feel like money disappearing every month for something they might not be using. Here's why pricing psychology matters.

The grey button that tells your user what's coming

Greyed-out features aren't broken UI. They're in-product marketing. They tell users what's coming next and create anticipation without cluttering the interface.

Your competitor's pricing is your research

Your competitor's pricing page is free market research. It tells you what people are willing to pay, how the market segments, and where the gaps are.

The refresh course your app was born to deliver

If your industry requires recurring certification or refresher courses, your app has a built-in retention loop that most consumer apps would kill for.

Your first five reviews will shape everything

Your first App Store reviews set the anchor for every user who finds you next. Here's why getting the first five right matters more than the next fifty.

The feedback form nobody fills out

You added a feedback button to your app. Nobody's using it. That's because the best feedback comes from what users do, not what they say.

Getting Started

You are the expert in the room

You don't have a tech background. But you know your industry better than anyone in the meeting. That knowledge is the most valuable input in the design process.

Getting Started

The mate who said it would never work

You told your mate about your app idea. They said 'that'll never work.' Here's why that feedback says more about them than it does about your idea.

The week between meetings where nothing happens (and everything happens)

The gap between design meetings feels like dead time. It's not. The best thinking, the best ideas, and the best decisions happen in the quiet periods.

Got an app idea?

Book a free 20 minute call. Tell me about your idea. I'll be honest about whether this is the right fit. And if it is, we can start within the week.

Book a free call