Ryan Phillips (Shopside)

That's awesome, congrats on the new role!

I'm feeling good about where Early Bird landed (😎) in 2024 and am equally excited about 2025.

We have a few things planned, such as integrating with Shopify Flow, adding support for the major email providers and continuing to refine the pre-order process.

Follow for more updates!

We're a majority engineering team and have no shortage of features to build and things to refine.

We are trying to dedicate more time to distribution. We have a product that we're proud of, now we need to spread the word.

😅 Oh and revenue. We need more of that to be sustainable for the long term.

The Bad.

😩 The 'Built for Shopify' review process was tedious. This deserves a thread of its own.

😡 We had fake stores attempt to use our email features to send phishing emails.

🤔 Selling plan UI doesn't play nice with all 'Add to cart' methods. We still needs to solve this one (Trade theme).

The Good.

📊 We’ve had hundreds of merchants run pre-order, backorder and back-in-stock campaigns.

💸 Our early adopters have sold almost $400,000 in pre-orders.

🛠️ We received our Built for Shopify badge.

🤯 Shopify told us that they use Early Bird as an internal example of a well-made app.

We’re building Early Bird - the most integrated and native-like pre-order app for Shopify.

https://buff.ly/3ZEMuae

🧵 Here’s a snapshot of how the first few months looked.

#shopify #shopifydev #shopifyapp #preorder

This is a great lead and makes perfect sense, I'll do some digging in this direction and see what I find.

Hello 👋

Same! I kinda just posted into the void hoping to find my people. Surely there are more of us out there!

This is for an embedded app inside the admin. The reason we want to bring the number down is the 2.5s benchmark is a requirement for the 'Built for Shopify' badge.

We just received the badge, but have already moved back above the threshold and have 60 days to bring it back down.

We’re running low on ideas on how we might improve this metric. We believe we’re doing everything we can to render the LCP element immediately.

I’d love to hear from others who have had the same issue; surely we can’t be the only ones!

As a CSR app, we need to show a interim screen while the data is fetching. We’ve confirmed that the LCP element is the loading screen. This element is rendered almost immediately and isn’t blocked by any API calls.

Our lowest scores are on the days with the most loads.

Coincidence or cache?

Here’s some context about our app:

It’s CSR. React + Vite. We reduced the bundle size as much as possible. 500kb Gzipped. Largest chunk is 180kb.

Hosted in an S3 bucket, sitting behind Cloudflare.

Our latest app has been having issues with it’s LCP.

We’ve made a bunch of changes to try and bring it down, but find ourselves stuck around 3.0s.

Are there any performance devs out there that might be able to give us some new ideas?

Technical details inside 🧵

#shopify #shopifyapp #shopifydev

👋🏻 Hello, I’m Ryan.

👔 Co-founder of Shopside, building apps for Shopify.
🦚 Early Bird: Pre-orders, backorders and back in stock.
📅 Bloom: Date picker for deliveries and in-store pickups.