An independent studio.

meshmesh Labs is independent and small. That is a constraint, and it is also the point: we ship fewer things, we own every line, and there is nobody to hand a difficult decision to. When this site says something does something, someone who wrote it checked.

Being small is usually described as a disadvantage that a studio grows out of. We think it is the only structure in which the answer to "should we collect this?" can reliably stay no. A bigger company would have a growth team, and a growth team has to justify itself. There is nobody here whose job depends on your data being interesting.

What we are building →

The name

Meshmesh — مشمش — is Arabic for apricot. The logo is an apricot drawn as software rather than as fruit: one circle, one seam, one leaf.

The seam is the whole mark. It is what makes an apricot read as an apricot rather than as an orange, and it is the only line in the drawing — which is why the mark still holds together at 16 pixels, when the leaf has dropped out and there is nothing left but a circle and a crease. The horizontal rules on this site are that same seam, reused. Once you have seen it you will not stop seeing it, and that is what a mark is for.

The wordmark is never re-set in Arabic — not in an Arabic build, not on Arabic stationery, not anywhere. One lockup serves every language.

The orange is #F58220, and it is a fill colour, never a type colour: at about 2.6:1 against white it is illegal as text under the accessibility guidelines, and every orange brand that looks cheap online broke exactly that rule. Orange text on this site is #A8480C or darker. You are looking at the difference right now.

What we will not do

• Sell your data. Not to advertisers, not to data brokers, not as part of an acquisition. There is no version of the business plan in which what you record in one of our apps is an asset on a balance sheet.
• Manufacture guilt. No streaks to break, no notifications engineered to pull you back, no leaderboard you did not ask to be on. Habit is not a growth metric, and an app that treats it as one is doing something worse than being annoying.
• Ship a feature we cannot explain. If we cannot say plainly what something sends and why, it does not go in — and "it is standard practice" has never once been an answer to that question.

How a thing gets built here

1. It has to be needed every day

   We are not interested in software you open twice. The test for a new app is whether someone would miss it on the third Tuesday.

2. It gets written twice

   Once to find out what it is, and once properly. The first version is research, and we throw more of it away than we keep.

3. The privacy decision comes before the feature

   What must never leave the device is decided at the schema, not at the end. It is far easier to build a fence than to remove data that has already been collected for a year.

4. It ships when it is right, not when it is due

   There is no investor calendar here. The upside of being small is that the only deadline is our own patience.

Craft, specifically

Typeface

IBM Plex, in both scripts — the Arabic and the Latin were drawn together, so a bilingual lockup does not look like two companies stapled together.

Platforms

iPhone, iPad, Apple Watch. Built in Swift and SwiftUI, with no cross-platform layer between us and the system.

Languages

Arabic and English are both first-class here, and right-to-left is treated as a layout in its own right rather than as a mirrored afterthought.

Offline

Anything that can be computed on the device is computed on the device. The network is for the things that genuinely need it, and for nothing else.

Accessibility

Dynamic Type, VoiceOver labels, contrast that passes at the smallest size we ship — not as a late audit, but as the reason a layout is shaped the way it is.

Talk to us

Arabic and English both welcome, and we read every message.
Ways to reach us →