Hülagühan Labs: who we are and how we work
We are a software studio based in İstanbul. We build products for clients and publish our own apps as well.
Hülagühan Labs has been working out of İstanbul since 2019. We build web applications, iOS and Android apps, SaaS products and interface design. We do this for clients, and we do it for our own products too — and the second part noticeably changes how we do the first.
The single-team model
The most common problem we saw in enterprise projects was not technical: well-planned work fell apart between teams at delivery. Design sat in one place, development in another, and responsibility for the launch usually nowhere at all.
That is why we chose the single-team model. The same people run discovery, design the product, write the code and submit it to the store. This model never made us a fast-growing agency — but it does let us stand behind every product we deliver.
We publish our own apps too
Whether a software studio really understands store processes only becomes clear once it has published an app of its own. We have.
FamSinyal is a family safety app in which parents pair openly and visibly with their child's device to use SOS alerts, an “I'm safe” signal and location sharing. It does not track covertly; the app is visibly running on the child's device. It is live on both the App Store and Google Play — see our Products page for details.
What we learn building that app flows straight into our client work: how to fill in privacy labels, how to explain the justification for a location permission to a review team, why the account deletion flow has to be in the first release. These are things you learn by shipping, not by reading documentation.
How we work
We split the process into five steps, and the output and duration of each are agreed up front:
- Discovery (1–2 weeks): Goals, constraints and success criteria are clarified. You leave with a technical discovery document and a prioritised scope.
- Design (2–4 weeks): Flows, interfaces and the design system are built. We agree on a clickable prototype before a line of code is written.
- Development (6–16 weeks): Two-week cycles. Every cycle ends with a working build and a demo.
- Launch (1–2 weeks): Load testing, security review, store submission and monitoring setup.
- Support (ongoing): SLA-backed support, security updates and improvement driven by measurement.
We don't deliver what we haven't agreed on
We write performance targets into the contract. LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1, and a 200 KB limit on JavaScript at first load. Once the number is in the contract, every new dependency that breaks the budget automatically starts a discussion — and having that discussion before release is far cheaper than having it afterwards.
We take the same approach to compliance. KVKK, GDPR and store requirements enter the design on day one. We don't do surprise compliance work in launch week, because the decisions about what data you collect and why are already made during discovery.
The code we hand over becomes yours
When we deliver a project, your team has to be able to develop it further. Documentation and training sessions are part of the job, not an extra. The rights of use in deliverables that have been paid for in full are transferred to you.
Getting in touch
All our communication runs by email. For project enquiries and proposal requests, write to info@hulaguhanlabs.com.tr; we usually reply within one business day. Briefly describe what you want to build, your goals and any timing constraints — we'll clarify the scope together.
