Editorial inbox · Oslo
Contact the ViewBinary Digital editorial team
Use this page to send a question, point out an error, or suggest a topic. Messages go to the editorial team, not a sales desk. We read everything, though replies may take a few days depending on volume.
Questions
Anything unclear in a guide — a term, a tradeoff, a step you are weighing for your own build.
Corrections
The most useful thing you can send. Tell us where a guide is wrong or explains something badly.
Topic suggestions
If one question keeps coming up in your own work, that is a good reason for us to write about it.
Messages we can act on
What to write to us about
Corrections are the most useful thing you can send. If a guide gets a fact wrong, explains something badly, or uses a term incorrectly, tell us and we will fix it. It helps to name the page and quote the line you are reading, so we can find the same sentence you did.
Topic suggestions are welcome too, especially if a question keeps coming up in your own work. If you and your team keep arguing about the same choice, say what the choice was and what makes it hard. That tells us more than a one-line request.
General questions about the guides are fine as well. We answer what we can from what the guides cover, and we will say so when a question sits outside that scope.
What we cannot help with
We are an editorial team, so there are requests we will always decline. Saying this upfront saves you a wasted email.
- We do not provide development services, quotes, or project estimates. If you need a build, this is the wrong inbox.
- We are not a referral service. We cannot recommend specific agencies or freelancers, and we do not keep a list of them.
- If your message is a request for paid work, we will not be able to help, and we would rather say that upfront than waste your time.
- We cannot review your product, app, or codebase, and we cannot comment on contracts, prices, or vendor selection for a live project.
Writing line
How to send a message
Use the form on this page. Include the page you are writing about if your message is a correction or a question about a specific guide. The more context you give, the easier it is for us to respond usefully.
For a correction, quote the sentence as it appears and say what it should say instead. For a question, a short line about the platform, size, or stage you are working at helps us answer in the right register.
Where we are
ViewBinary Digital
Parkveien 15, 0350 Oslo, Norway
Monday to Friday, 9:00 AM – 6:00 PM
Editorial contact form
Fields marked with an asterisk are required. We use what you send only to read and reply to your message.
From inbox to update
What happens after you send
Your message arrives in the editorial inbox. We read it, and if a reply is needed, we respond by email.
The message lands
It goes to the people who write and check the guides. No routing, no queue ticket, no auto-reply loop.
We read and reply
If an answer is needed, it comes back by email. If the point is already covered in a guide, we will link you to the section that covers it.
Corrections get checked
A correction is reviewed against the relevant guide and the page is updated where the change is warranted. You do not need to chase it.
Suggestions get logged
Topic suggestions are recorded and considered when the next guides are planned. A suggestion that fits the editorial scope may be written later.
Reply pace
Response times
This is a small team, so replies are not instant. Expect a few working days. If your message is time-sensitive, say so in the subject line and we will do what we can.
Messages that arrive over a weekend or a public holiday are read on the next working day. Corrections that only need a wording fix are usually the fastest to close.
Your data
We use the information you send only to read and respond to your message. We do not sell it, and we do not add you to a mailing list. If your note leads to a correction, we may keep it until the guide has been updated so we can confirm the change matches what you reported.
Details on how personal data is handled, how long it is kept, and how to ask for a copy or deletion are set out in the privacy policy. You can also read the cookie policy and the terms of service for the full picture.
Phone
Address
Parkveien 15, 0350 Oslo, Norway
Working hours
Monday to Friday, 9:00 AM – 6:00 PM
Before you write
Questions we get about writing in
Do I need to be a developer to write in?
No. Most corrections we receive come from people who ran into a problem while briefing a build, not from people writing code. If a sentence in a guide does not match what actually happened on your project, that is worth sending.
Will you tell me which platform or vendor to pick?
We will not name a specific agency or freelancer, and we do not give project estimates. What we can do is point you to the guide that explains how the tradeoffs work, so you can ask better questions of whoever you hire.
How much detail should a correction include?
Name the page, quote the sentence you are reading, and say what it should say instead. If the problem is a missing caveat rather than a wrong fact, describe the case where the current wording misleads. That is usually enough for us to check it.
Can I suggest a topic that is not covered yet?
Yes, and it is one of the more useful things you can send. Tell us the decision you are trying to make and what makes it hard. Suggestions are recorded and considered when the next set of guides is planned.
Where to find us
The office behind the guides
The editorial team works from Parkveien in Oslo. Most correspondence happens by email, which is the fastest way to reach us during working hours.
Office address
ViewBinary Digital, Parkveien 15, 0350 Oslo, Norway
Keep reading
How custom build, platform, and cross-platform paths differ for a web or mobile project.
What common frameworks and tools are used for, and when a simpler stack is enough.
How to scope a build, what to decide first, and where plans usually go wrong.
Practical questions to put to any team before a project begins.