Your mobile app, from the brief to the store
I build software from Belém, in northern Brazil, and have done since 2020. You come with an app to build, a codebase somebody else wrote and nobody wants to open, or a library you would rather license than rebuild. From the first email to the handover, you deal with me.
- Apps published to Google Play and the Microsoft Store
- Signed contract and nota fiscal
- Code, credentials and store accounts are yours at the end
8 years of software work, my own company since 2020
Freelance backend at IssueHunt from 2018 to 2019. Mobile developer at VoxData from 2019 to 2022, and at Idopter Labs since 2022. Independent security research on HackerOne runs alongside it, since 2018 and still active.
What you can check right now
Every number here is a link.
What you can hire
Three shapes of work: something built from a scope written down before it starts, a licence for something already published and maintained, and a second reading of something that already exists.
A mobile app, built and shipped
Your app from the brief to a listing live on the store. I have handled store submission inside companies since 2019.
- Flutter and React Native, with native Kotlin and Swift where your app needs it
- Publishing to Google Play and the App Store, including answering the review team when they reject a build
- Firebase, CI/CD pipelines and automated tests set up with the project
- Native modules in Swift, Objective-C, Java and Kotlin, bridged into the React Native codebase you already have
A licence for something already built
License a package or an app I already maintain, instead of paying to have it built again and then waiting for it.
- Open source packages already published on npm, PyPI, LuaRocks and the AUR
- Apps already live on Google Play and the Microsoft Store
- Developer tooling published as open source packages, source and licence included
- Commercial licensing and support for anything already released
A second pair of eyes on your codebase
Your app is failing store review, or the developer who built it left. I read the codebase and work with the team that keeps it running.
- Security assessment and code review of your mobile app, by someone reporting flaws through HackerOne since 2018
- Architecture review of your React Native or Flutter codebase, with the findings written down
- Release engineering: pipelines, feature flags and staged rollouts
- One to one mentoring for the engineers who will own the code after I leave
Who this works for, and who it does not
Three cases that work well, and three I turn down. Better you know now than after signing.
A project with a closed scope
You know roughly what the app has to do, and you want a price, a deadline and a list of exclusions in writing before anything starts.
A codebase somebody else wrote
Your app is failing store review, or the developer who built it is gone and nobody left on the team has opened the project. I read it and tell you what I find.
A licence and support for something already published
You need a library or an app that already exists and is already maintained, and you would rather license it than pay to have it built a second time.
Not this: A developer allocated to your squad
I do not sell headcount or full-time availability. I do the work, and the calendar is agreed project by project.
Not this: Hourly work with no scope
With no written scope and no definition of done, the conversation ends up being about the invoice. With one, you know the price before anything starts and I know when I am finished.
How your project runs
The same four steps on every contract.
- 01
Scope
You describe the problem. I come back with what I understood, what I would build and what I would deliberately leave out. That first pass is free and binds you to nothing.
- 02
Written estimate
Price, deadline and everything outside the scope, in writing. Nothing starts before you have that document.
- 03
Iterative delivery
Builds you can install and open, on a fixed cadence. You see your app running long before it is finished.
- 04
Handover
Source code, credentials, store accounts and documentation are yours at the end. Support after that is a separate agreement you choose to sign.
What I build with
The stack behind the work above, grouped the way it is used on a project.
- Mobile Development
- FlutterReact NativeXamarinJavaKotlinObj-CSwiftSwiftUIJetpack ComposeIonic
- DevOps
- FirebaseGitLab CI/CDGitHub CI/CDAzureGoogle CloudDocker
- Soft Skills
- LeadershipTeam ManagementProblem SolvingCommunicationOrganization
- Frontend
- HTMLCSSJavaScriptTypeScriptReactVue.jsTailwind
- Backend
- Node.jsExpressElixirPostgreSQLSQLite
- Design
- FigmaMobile UX
- Game Development
- UnityFlameLÖVEPixel ArtBlender
Company details
Public data from the register held by the Receita Federal, the Brazilian federal tax authority.
- Legal name
- TIAGO DANIN TECH SOLUTIONS LTDA
- Trade name
- Tiago Danin Tech Solutions
- CNPJ
- 67.171.570/0001-15
- Legal form
- Sociedade Empresária Limitada, a Brazilian limited company
- Size
- Microempresa, the register's micro-enterprise bracket
- Tax regime
- Simples Nacional
- Register status
- Active
- Operating since
- October 2020. The current CNPJ dates from June 2026, when the business changed legal form from Empresário Individual, the Brazilian sole trader registration, to a limited company. Same owner, same principal activity and same city as the registration it replaced.
- Managing partner
- Tiago Jatahy Danin, sole managing partner
- Primary activity
- 6201-5/01 Custom computer program development
- Secondary activities
- 6203-1/00 Development and licensing of non-customisable programs6204-0/00 Information technology consulting
- Location
- Belém, Pará, Brazil
Tell me the problem and I reply with a scope
I read and answer the email myself. Send it unfinished: four lines are enough, saying what the product is, who it is for, the deadline if there is one, and the budget range if there is one.
CNPJ 67.171.570/0001-15, signed contract, nota fiscal, Simples Nacional. Remote, from Belém.