Heeey! What’s up?

Before starting this email, a quick reminder:

On May 27, we’re hosting The Wide Event, from 6:00 pm to 11:30 pm, in Paris, at “Le Salon Des Miroirs”.

It’s a special Shopify partners Event (in English) for the whole ecosystem.

Merchants and Shopify Agencies will be there, it’s a good way for you to find customers.

App Founders will be there, it’s a good way for you to find partners.

But it’s also great to network and get inspiration and motivation!

150 people are expected, so hopefully you’ll be one of them!

Get more details about the event by clicking on the image below 👇

In today’s email we’re going to talk about:

• Built For Shopify

• You have to switch from Rest to GraphQL

• The Shopify Editions event

Let’s go!

Built For Shopify

WideBundle is now Built For Shopify! Finally! After a bit more than 2 months!

And you know what’s crazier?

We’re not using Shopify Polaris! 😳

Many people thought it was impossible. But since the beginning, Shopify always said that using Polaris was recommended, not mandatory.

It was recommended because they have design guidelines. These guidelines are already respected by Polaris. Which is why it made sense to use it.

But WideBundle never used it since the beginning.

You already know me, I hate doing things like everyone, haha!

I’m using vanilla PHP, I’m being transparent even with the numbers, and obviously, I don’t use Polaris!

Well… Before sharing with you the impact it had on my app, let me share with you why I decided to get BFS (and if you should get it too)

Why did I decide to get BFS?

Starting in December, we slowly lost ranks on some keywords.

Some keywords whose ranking hasn’t changed for years. So something was wrong.

I took a piece of paper, my brain, and some javascript and spent hours analyzing everything:

Number of reviews, velocity, change in ranking, etc…

I came to this conclusion: Even though BFS didn’t have a big impact in the first few months, it’s now obvious that it has changed.

Having BFS now has a big impact on your ranking.

When should you go for BFS?

• Your app is new

• You lost many ranks for your keywords in the last few months

• You’re not at the top of your keywords

When shouldn’t you go for BFS?

• You don’t rely on the App Store for your installs

• You’re already at the top positions for your main keywords.

Getting started

The first step is to check a few points. Even before thinking about the design guidelines.

And the most complicated for people is the section “Build for performance”…