Mobile apps
Native apps for iOS, Android and Huawei, where a web app on the home screen is not enough.
- Opens
- On the phone
- Gets there
- From the app store
WHAT WE BUILD · APPS
Apps for the phone, Telegram, the browser and the desktop
Four kinds of app, built to the same standards and ownership terms as everything else we build. You own the code of each one.
Mobile app
Telegram mini app
Browser extension
Native desktop app
FOUR KINDS OF APP
Where it opens decides which one fits
Each kind lives in a different place. Pick the place your people already work in.
Telegram mini apps
A full app that opens inside Telegram, where your customers already write to you.
- Opens
- Inside Telegram
- Gets there
- Nothing to install
Browser extensions
A tool that sits in your team’s browser and works on the pages and systems they already use.
- Opens
- In the browser
- Gets there
- Added to the browser
Native desktop apps
For work that needs the whole computer: local files, long sessions and several screens at once.
- Opens
- On the computer
- Gets there
- Installed on it
MOBILE, IN DEPTH
Mobile has its own pages
Everything we build is mobile-first and installs to a home screen without an app store. These pages cover it in full.
Web app or native
Everything installs to a home screen by default. Native where the device features require it.
MobileProgressive web apps
A website that behaves like an installed app: on the home screen, full-screen, no app store.
Progressive web appsNative apps
The exception, not the default: for the feature that a browser cannot reach.
Native appsTelegram bots
A bot works in the chat itself, on Telegram’s own Bot API. A different build from a mini app.
Telegram botsWHAT WE CAN SHOW TODAY
Done work, and what we build
We publish which kinds we have delivered, and which we build, and keep the two apart.
| Mobile apps | For iOS, Android and Huawei. Clients not named. | DONE |
|---|---|---|
| Telegram mini apps | Among what we build. | WE BUILD |
| Browser extensions | Among what we build. | WE BUILD |
| Native desktop apps | Among what we build. | WE BUILD |
HOW AN APP PROJECT RUNS
The same six steps as every project we build
The process of every Gigagrams project, from the brief to care after launch.
01
Your answers
People write the brief
Built from your own answers, one question at a time. Not written by AI.
02
Signed by both
The project passport
One card per question. Both sides sign off on the same text.
03
3 rounds per
milestone
Staging, with your comments
A private copy of the app. Comment on any part of it.
milestone
04
Score with date
and method
Stress tests
Speed, enterprise cybersecurity, function, QA and UX/UI.
and method
05
You own it
from day one
Launch
The work goes live after your review and the tests.
from day one
06
90 days
Care
Defects in our work fixed at our cost, then a care plan.
Our approach
Each step, and the reason for it.
STRAIGHT ANSWERS
Questions about apps
Gigagrams builds four kinds of app: mobile apps, Telegram mini apps, browser extensions and native desktop apps. Mobile apps for iOS, Android and Huawei are work we have done. Each app is built to the same standards and ownership terms as everything else we build, and you own the code of each one from day one.
Most projects do not need a store app. Everything we build is mobile-first and installs to a phone home screen without an app store. Native is used where a device feature requires it, such as offline use, background location or push at scale. Which one a project needs is scoped during the technical audit, not assumed from the start.
A Telegram mini app is a full app that opens inside Telegram, where your customers already write to you. There is nothing to install and no app store. It is a different build from a Telegram bot, which works in the chat through messages and buttons. We build bots too, on Telegram’s own Bot API.
A browser extension makes sense for a tool your team uses on the pages and systems they already work in. A native desktop app makes sense for work that needs the whole computer: local files, long sessions and several screens at once. Both start from your answers, one question at a time, before anything is built.
Tell us where your people work. We build the app for that place.
We ask one question at a time, and your answers become the project passport.