Evez.

Mical Robert

Editor, Evez. Mical Robert writes and maintains the 39 Snapchat guides on Evez, across 7 topic areas.

In short

I write about one app, in depth, and I keep the guides current as it changes. Every claim here is either something you can check in Snapchat yourself or something with a named source attached. Where I do not know, the guide says so.

How I got here

Not through Snapchat, oddly. I got here through being the person other people asked. If you are the one in a family or a friend group who is assumed to be good with phones, you will know the pattern: someone hands you a device, says “it just started doing this,” and expects an answer.

With most apps you can work it out in a minute. Snapchat was the one that kept defeating me. Not because it is complicated underneath, but because it hides almost everything behind gestures rather than buttons, labels very little, and rolls changes out to some accounts weeks before others. Two people on the same phone, on the same version, can be looking at different screens. I would find the setting, explain it, and a month later it had moved.

So I started writing things down. First for myself, so I would not have to rediscover the same menu twice. Then properly, with sources, because I kept finding that the confident answer at the top of the search results was wrong, or three versions out of date, or quietly invented by somebody who had never opened the app.

That is the whole origin story. There is no more glamorous version of it.

What I actually do before publishing

The method matters more than the biography, so here it is in full. Every guide on this site goes through the same five steps.

  1. Start from the real questionPhrased the way people actually ask it, not the way it reads well. If the honest answer is “you cannot do that,” the guide says so in the first paragraph rather than burying it.
  2. Check the primary source firstSnapchat’s own documentation, then regulator publications and company filings. Never another blog. 117 sources are cited across the library and every one is named and linked, so you can check me.
  3. Open the app and try itMenu paths get verified rather than copied. This is where most published Snapchat advice falls over, because the path changed and nobody looked.
  4. Mark what variesRollouts differ by account, device and country. Where behaviour is inconsistent I say so, instead of picking the version that makes a tidier sentence.
  5. Date it, then come back to itEvery guide carries the date it was last checked, and gets revisited when Snapchat ships something that affects it. For an app that changes this often, that date is part of the information.

What I refuse to write

Most of what is published about Snapchat is wrong in the same handful of ways. These are the rules I hold to, and they cost traffic.

Independence

Evez has no connection to Snap Inc. Nobody at Snap reviews these guides, and no advertiser has ever seen one before publication. That independence is the point: it is what lets a guide say a feature is badly designed, or that a change is worse for you.

Where I am most likely to be wrong

Worth saying plainly, because every author page claims accuracy and almost none says where the risk is.

If the app disagrees with something I have written, the app is right. Tell me at contact@evez.online and I will check it, fix it, and update the date so other readers can see it moved. A correction is genuinely the most useful message I get.

What I cover

Recent guides

The full standards this site is written to, including the corrections policy and how sources are weighted, are on the editorial standards page.