A Developer Community Spotlight with Mark Thomas
Not many people can say they’ve attended 25 Apple Worldwide Developers Conferences (WWDCs), but Mark Thomas isn’t your average UK-based developer. As the founder of Appnalysis, an ACT | The App Association member company, Mark has spent his career digging deep into what makes apps usable, scalable, and impactful. From helping early-stage founders decode user behaviour to consulting with enterprise teams, Mark’s work sits at the intersection of UX, data, and digital growth. But Mark doesn’t just build apps, he builds community. Whether he’s exchanging ideas at our very own Dr. Funk’s Tech House or advising startups on go-to-market strategy, he’s seen firsthand the value of gathering, sharing, and speaking up.
In this Developer Community Spotlight, Mark shares what continues to draw him to WWDC, how the developer landscape has evolved, what today’s UK startup climate looks like for founders seeking to grow, and why staying connected to a broader community through events, conversations, and shared advocacy still matters.
Q&A with Mark Thomas
Let’s start at the beginning! Can you tell us a little about yourself and how Appnalysis came to be?
I’ve spent three decades in software, starting back when “cross-platform” meant literally writing separate builds for Windows, Mac, and even game ports. I developed MacDX technology, which powered ports like WipeOut 2097 and Kick Off.
I’ve been on the Mac platform since the Mac Plus days, first using Think Pascal and then MPW. When the App Store launched, I built one of the first Wi-Fi apps for the UK market. Along the way I founded and ran a 40-person agency and mentored more than a hundred engineers. That experience gave me a front-row seat to how the App Store has matured. It was once a world where small teams could make a splash. Today quality, security, discovery, and compliance are all higher bars to clear. I started Appnalysis to help agencies and the teams supporting development gain clarity in that landscape.
You’re truly a WWDC veteran; attending 25 conferences is no small feat! Thinking back to your very first one, what stands out to you as the biggest changes over the years?
When I first attended in 1998, WWDC was almost unrecognizable compared to today. Back then, the swag alone could kit you out as a developer — T-shirts, bags, even leather jackets. It was a great way to get fully kitted out, although your partner might have other views. They even used to host a movie night, which I still miss (though this year we did get one with the new F1 film).
There were hardly any queues; you could turn up an hour before and still find a seat. The atmosphere was calmer, and conversations flowed more naturally. Today the scale is enormous, and queues are part of the deal. But one thing has not changed. The real value is access to Apple engineers, and that one-on-one time remains the most important part of WWDC.
What continues to make attending WWDC a priority for you? Why keep coming back year after year?
WWDC is about getting back into the mindset of being an engineer and a solution provider. It is not just the sessions, it is the conversations, the questions, and the chance to talk through problems directly with Apple engineers. It is also grounding. Seeing how other developers use Apple’s technologies and reflecting on those patterns has been part of what shaped Appnalysis. It is a reminder that the ecosystem is always evolving, and we need to keep learning alongside it.
Do you think your decision to keep coming back says something about the investment landscape for global startups right now? Especially comparing the UK to the Bay Area.
For me, coming back to WWDC is almost soul food. I use the week to reset as an engineer, to observe how people are using mobile, how businesses are adopting technology, and to get a feel for what is happening in the ecosystem. My partner and I usually add a few days afterwards as a mini holiday, so the trip becomes a mix of reflection, observation, recharging, and a bit of downtime.
That said, being here does highlight the investment landscape. The Bay Area has a density of incubators and accelerators that you just don’t see in the UK, and a much more positive approach to risk. Investors are quicker to back ideas knowing not all will succeed. That contrast makes me think harder about how we scale in the UK and Europe, and how credibility is built differently across regions. It probably explains why so many of the biggest developer events are U.S.-based. Even this year, during WWDC, there was a massive AI and Data conference hosted by Databricks across almost all the Moscone Center buildings — a reminder of the sheer level of interest and investment clustered here.
As a founder navigating these challenges, how important is it to have spaces where developers can connect and share experiences at places like WWDC and Dr. Funk’s Tech House?
Well, first of all, developers do need to be fed and watered! Smiles. But seriously, spaces for networking are hugely important. Some of the best conversations happen in queues. Someone explains a problem and the person behind them has the solution. The same thing happens at community parties like Dr. Funk’s Tech House, where you see products strike a chord and contacts being exchanged. Those informal spaces make the community stronger. They are where ideas are shared, problems solved, and opportunities born.
You’ve seen the developer community evolve over decades. What makes you feel hopeful about where it’s headed?
The developer community has widened from agencies and product teams to policy groups and regulators and that makes it more complex than ever. There are more vectors to consider: software development kit (SDK) risks, monetisation, compliance, security.
But what gives me hope is how the culture has shifted. Developers, agencies, even regulators are more open to sharing what works and what doesn’t. You hear conversations now that simply wouldn’t have happened 10 years ago. That shift toward openness and collective problem-solving is what keeps me optimistic.
And it’s also why I built Appnalysis. When people come to the table with clarity, backed by data, the conversations themselves become more productive decisions get made faster, and teams can focus on what really matters.
Before we wrap up, is there any advice or perspective you’d want to leave with fellow developers in the community?
I would leave with this: development is not just code. The business and product journey matters just as much. It is not only about Xcode, frameworks, or your favourite no-code SDK. Success also depends on discovery, monetisation, compliance, and security.
Always keep learning. Do not rely only on what your employer provides. If you are interested in a technology or an event, see if you can negotiate support — many employers will contribute expenses or allow paid leave — but be prepared to invest in yourself too. You are building your own career and doing nothing is the only option that makes no sense. And do not underestimate the value of your peers. Your competitors are your peers too, and learning from them is vital. That is why I value organisations like the App Association. It creates a space for clarity, perspective, and growth across the whole community.