Building Apps That Actually Work
We started flowtechneuron in 2019 because we got tired of seeing businesses struggle with mobile apps that looked pretty but fell apart when people actually tried to use them. Six years later, we're still here doing what we love – creating iOS and Android apps that solve real problems for Taiwan businesses.
The Beginning
Back in 2019, I was working as a freelance developer while my co-founder Konrad was at a tech company in Taipei. We both kept running into the same problem – clients needed mobile apps, but most development shops either charged way too much or delivered apps that broke constantly.
So we decided to do something about it. Started with just the two of us in a tiny office space in Douliu, taking on small projects for local businesses. Our first app was for a restaurant chain that needed a simple ordering system. Nothing fancy, but it worked perfectly and they're still using an updated version today.
The People Behind The Code
We're a small team, which means you'll actually get to know the people working on your project. No account managers or middlemen – just developers who care about getting things right.
Konrad Thorne
Konrad's been writing iOS apps since 2016 and has this weird ability to spot potential problems before they actually happen. He's the guy who insists we test everything twice and then test it again. Originally from Sweden but has been in Taiwan since 2018. When he's not coding, he's probably hiking somewhere in the mountains.
Viktor Lundgren
Viktor joined us in early 2021 after getting frustrated with enterprise development at a big corporation. He's the Android expert who can make apps work smoothly even on older devices. Has this philosophy that good code should be readable by humans, not just machines. Spends his free time contributing to open source projects and teaching his neighbor's kid how to code.
What We Actually Believe In
These aren't just nice words on a website. They're the principles that guide every decision we make, from the code we write to how we communicate with clients.
Build It Right
We'd rather spend extra time doing something properly than rush it and fix problems later. Clean code, proper testing, and thinking through edge cases – that's just how we work.
No Tech Jargon
When we explain technical stuff, we use plain language. You shouldn't need a computer science degree to understand what we're doing with your project.
Solve Real Problems
Features should exist because they help your users do something better, not because they look cool in a demo. We'll push back if something doesn't make sense.
Honest Timelines
We give realistic estimates and stick to them. If something's going to take three weeks, we won't promise it in one just to win the project.
