MELBIL LTD

This studio builds mobile applications

The work has gone on for years. The apps run on iOS and Android. Building one means deciding how it should behave, making it, and bringing it to a version a person can install. We hold to that order on every app. The behavior comes first, the making follows, and the installable version is where the work has to land.

A person should be able to put the app on a phone and open it. That is the version we work toward. We decide what the app must do, we make the parts that carry that behavior, and we keep going until the build can be installed. iOS and Android both get that version. We do not stop at a description of the app.

The same path applies from one app to the next. We name the behavior, we build it, and we hand over a version a person can install. That is the work MELBIL LTD does.

A coast seen from above

iOS and Android

A product is made for both iOS and Android. We do not finish one system and treat the other as a later copy. The behavior is chosen for both, the making covers both, and the version a person can install exists for both.

A person on either phone should meet the same tasks and the same limits. We check the app on each system before we call the version ready. The two builds stay aligned because they come from one set of decisions about how the app should behave.

The path of a project

A project starts from what the app needs to do. We write down the tasks a person should be able to finish. We decide how the app should behave when those tasks go well and when they fail. Then we make the app.

Making means the screens, the logic, and the checks that the behavior holds. The path ends at a version someone can install. That version is what a person puts on a phone and opens. We do not leave the work at a sketch. The installable build is the result we owe the project.

The assistant

The product includes an assistant. People can talk with it. It is not a human and it is not professional advice. What they write is used to answer that conversation. Those words are not passed to other users.

The assistant reads the message in that exchange and replies for that exchange only. It does not hand the text to another person who uses the app. It does not speak as the studio and it does not give professional advice. If you want a person here to read about an app, write to us by email. That letter stays outside the conversation in the product.

Data

The app does not build a personal profile. It does not keep a name, an email, a phone number, or a precise place as account data. Users do not send personal data to each other. Nothing in the app is there for one person to hand those details to another.

Attribution uses Singular. Pushes use OneSignal. The identifying item for both is a unique id. That id lets measurement and delivery work without a personal profile. The account of this is on our Privacy page.

Concrete, a shadow, and one opening

Write to us

MELBIL LTD is the developer. If you want to talk about an app, write and say what it should do, who it is for, and what a person should be able to finish in it.

We read what you send and answer from the studio. The address is [email protected]. The letter is separate from the app and contains only what you wrote. Read Privacy and Terms for how the apps treat data and what use we accept.