tr]:last:border-b-0',
46 | className,
47 | )}
48 | {...props}
49 | />
50 | );
51 | }
52 |
53 | function TableRow({ className, ...props }: React.ComponentProps<'tr'>) {
54 | return (
55 | |
63 | );
64 | }
65 |
66 | function TableHead({ className, ...props }: React.ComponentProps<'th'>) {
67 | return (
68 | [role=checkbox]]:translate-y-[2px]',
72 | className,
73 | )}
74 | {...props}
75 | />
76 | );
77 | }
78 |
79 | function TableCell({ className, ...props }: React.ComponentProps<'td'>) {
80 | return (
81 | | [role=checkbox]]:translate-y-[2px]',
85 | className,
86 | )}
87 | {...props}
88 | />
89 | );
90 | }
91 |
92 | function TableCaption({
93 | className,
94 | ...props
95 | }: React.ComponentProps<'caption'>) {
96 | return (
97 |
102 | );
103 | }
104 |
105 | export {
106 | Table,
107 | TableBody,
108 | TableCaption,
109 | TableCell,
110 | TableFooter,
111 | TableHead,
112 | TableHeader,
113 | TableRow,
114 | };
115 |
--------------------------------------------------------------------------------
/src/content/blog/custom-tracks.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Custom Update Tracks
3 | author: bryanoltman
4 | description: Announcing the ability to create custom tracks
5 | date: 2025-05-30
6 | cover: custom-tracks-cover.png
7 | ---
8 |
9 | Shorebird now supports custom update tracks!
10 |
11 | Shorebird has long supported “staging” and “beta” environments for testing your
12 | patches before deploying them to users. However, now we have added the ability
13 | to create an unlimited number of tracks with custom names.
14 |
15 | Shorebird does not collect any information about your users. As a result of our
16 | privacy-forward design, Shorebird has no ability to provide things like region-
17 | or group-based rollouts of patches, A/B testing, etc. out-of-the-box. However,
18 | we provide a rich API set to enable you to implement all of these from within
19 | your own apps. Previously, these APIs were limited to operating on a fixed
20 | number of tracks (“staging”, “beta”, and “stable”), but now you can use an
21 | arbitrary number of tracks and push separate patches to each one should you
22 | wish. This can allow you to roll out updates with as much precision as you would
23 | like.
24 |
25 | To use these new features, first ensure you’re using package:shorebird_code_push
26 | version 2.0.4 or later. Update your pubspec:
27 |
28 | ```yaml
29 | dependencies:
30 | shorebird_code_push: ^2.0.4
31 | ```
32 |
33 | Once that’s done, `Updater.checkForUpdate` now can receive any string as an
34 | UpdateTrack. Check out our
35 | [package docs](https://pub.dev/documentation/shorebird_code_push/2.0.4/shorebird_code_push/UpdateTrack-extension-type.html)
36 | for more details on this.
37 |
38 | For example if your organization has a longer multi-track approval process, or
39 | your own custom update process you might need more tracks:
40 |
41 | ```dart
42 | final track;
43 | if (user.isQa) {
44 | track = UpdateTrack('qa');
45 | } else if (user.isDev) {
46 | track = UpdateTrack('dev');
47 | } else if (user.isDesigner) {
48 | track = UpdateTrack('down-stream-test');
49 | } else {
50 | track = UpdateTrack.stable;
51 | }
52 |
53 | updater.checkForUpdate(track:track);
54 | ```
55 |
56 | Or for example if your app is required to change or disable a behavior within a
57 | specific region (e.g. as part of legal or compliance changes):
58 |
59 | ```dart
60 | final UpdateTrack updateTrack;
61 | if (user.requiresLegalUpdates) {
62 | updateTrack = UpdateTrack('legal-update');
63 | } else {
64 | updateTrack = UpdateTrack.stable;
65 | }
66 | ```
67 |
68 | Note that the name “stable” is still special in the sense that it is the
69 | default. If you call updater.checkForUpdate() without a track argument, it will
70 | default to “stable”. There is currently no way to change the default track used
71 | by our C++ “auto_updater” code, however when the auto_updater is disabled, you
72 | can use whatever default track you like when calling checkForUpdate.
73 |
74 | These new features are supported in every version of Flutter that Shorebird
75 | supports, and because this update only includes Dart changes, it's even possible
76 | to even to start using these new features via a patch.
77 |
--------------------------------------------------------------------------------
/src/content/blog/seed-round.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Accel Leads $3M Seed Round in Shorebird
3 | author: shorebirdtech
4 | description:
5 | Shorebird has raised $3M to expand its suite of Flutter developer tools,
6 | including Code Push and Shorebird CI, making mobile iteration faster than
7 | ever.
8 | date: 2025-09-23
9 | cover: 'seed-round-cover.png'
10 | ---
11 |
12 | We at Shorebird, a developer tools company founded by the creators of Flutter,
13 | have raised a $3M seed round led by
14 | [Dan Levine of Accel](https://www.accel.com), with participation from leading
15 | founders and operators across the ecosystem. Investors include Paul Copplestone,
16 | Miguel de Icaza, Andrew Lee, Jessica McKellar, Chris McKillop, Andrew Miklas,
17 | Neha Narkhede, Yuri Sagalov, and Linus Upson.
18 |
19 | Shorebird helps businesses succeed with Flutter. We started this journey by
20 | solving one of the biggest pain points in mobile development: slow release
21 | cycles. Our first product, Code Push, enables developers to deliver instant
22 | over-the-air updates to Flutter apps across iOS, Android, and Desktop Systems,
23 | bypassing traditional app store review bottlenecks. Already, millions of users
24 | receive updates powered by Shorebird every day.
25 |
26 | ## Expanding Products and People
27 |
28 | With this round, Shorebird has been able to accelerate product development,
29 | start its team, and expand its platform beyond Code Push. Most recently, we
30 | launched our second product [Shorebird CI](/blog/introducing-shorebird-ci), a
31 | zero-config continuous integration system built exclusively for Flutter and
32 | Dart. We are currently [hiring for a few new roles](/jobs), and are excited to
33 | bring more talented people into the team to help build faster, support more
34 | customers, and invest even more in the Flutter ecosystem.
35 |
36 | 
37 |
38 | “Mobile development has always lagged behind the web when it comes to speed of
39 | iteration,” said Eric Seidel, CEO of Shorebird and creator of Flutter.
40 | “Shorebird is here to change that. With Code Push and now Shorebird CI, we’re
41 | making Flutter development faster, more reliable, and better aligned with how
42 | modern teams build software.”
43 |
44 | “We’re excited to back Shorebird at this very early stage,” said
45 | [Dan Levine, Partner at Accel](https://www.accel.com/people/daniel-levine#bay-area).
46 | “Eric and the team bring unmatched expertise as the original builders of
47 | Flutter. Shorebird is solving a critical challenge for millions of developers
48 | and companies, and the early traction they have proves this is a
49 | category-defining opportunity.”
50 |
51 | ## About Shorebird
52 |
53 | Founded in 2023 and based in San Francisco, Shorebird builds products to help
54 | businesses succeed with Flutter. Our flagship service, Code Push, enables
55 | instant app updates without app store delays. Shorebird was founded by Eric
56 | Seidel, creator of Flutter, alongside Felix Angelov (creator of Bloc and Mason)
57 | and a small team of influential Flutter contributors.
58 |
59 | 
60 |
--------------------------------------------------------------------------------
/src/content/blog/yearly-plans.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Introducing Yearly Plans
3 | author: shorebirdtech
4 | description:
5 | We’re excited to roll out Yearly Plans for Shorebird designed to give you more
6 | flexibility and predictability as you build and scale your apps.
7 | date: 2025-04-23
8 | cover: 'yearly-plans-cover.png'
9 | ---
10 |
11 | We’re excited to roll out Yearly Plans for Shorebird. These plans are designed
12 | to give you more flexibility and predictability as you build and scale your
13 | apps.
14 |
15 | ## Why Yearly Plans?
16 |
17 | As our customer base has grown, so has the demand for yearly plans. Based on
18 | your feedback, the need typically comes down to two main reasons:
19 |
20 | 1. **Purchasing Process** - We’ve heard from many of you that yearly plans are
21 | essential to your internal purchasing processes—whether you’re part of a
22 | large organization with budget cycles or a small team looking to simplify
23 | payments. Some teams need yearly invoicing for budgeting, while others just
24 | want the convenience of avoiding monthly billing fluctuations.
25 | 2. **Unable to Predict Monthly Volume** - When starting with a new service, it’s
26 | tough to know how your team will use it until you dive in and experiment.
27 | We’ve seen usage spikes when business-critical issues arise are the moments
28 | when fast patches matter most but weren’t accounted for in the monthly
29 | budget. Whether you’re launching a new feature, onboarding users, or running
30 | a seasonal campaign, monthly patch usage can vary wildly. Picking the “right”
31 | monthly plan can become a headache.
32 |
33 | With our new yearly option, these issues are a thing of the past.
34 |
35 | ## How It Works
36 |
37 | - **One payment. 12 months of Shorebird.** Pay once upfront and get a full year
38 | of access to Shorebird. No more chasing monthly invoices or wrangling with
39 | payment systems.
40 | - **Patches credited upfront.** You’ll receive your entire year’s worth of
41 | patches on day one. Use them when you need them—whether you’re shipping daily
42 | or ramping up after a big launch. You can go beyond our typical monthly
43 | limits, as long as you stay within your new annual total. That means freedom
44 | to move fast when it matters most.
45 | - **No overages, no surprises** With our yearly plans, what you pay upfront is
46 | it. No surprise charges. This means you can scale your patch usage during busy
47 | times and slow down during quieter periods all without worrying about trigging
48 | unexpected fees.
49 |
50 | ## Who’s This For?
51 |
52 | Anyone can sign up for Yearly Plans as its available starting today via our
53 | Shorebird Console. Not sure if it’s right for you? Here are some use cases that
54 | inspired this update:
55 |
56 | - Teams who want predictable billing
57 | - Companies with seasonal usage patterns
58 | - Anyone who wants to prepay for peace of mind
59 |
60 | ## How to Switch
61 |
62 | You can upgrade to an annual plan right from the
63 | [Shorebird Console](https://console.shorebird.dev), or reach out to us via our
64 | [Discord Server](https://discord.gg/shorebird) if you have questions or want to
65 | talk through your options.
66 |
--------------------------------------------------------------------------------
/src/components/pricing/pricing-faq.tsx:
--------------------------------------------------------------------------------
1 | import { Markdown } from '@/components/ui/markdown';
2 | import {
3 | Accordion,
4 | AccordionContent,
5 | AccordionItem,
6 | AccordionTrigger,
7 | } from '@/components/ui/accordion';
8 |
9 | const faqs = [
10 | {
11 | question: 'How many patch installs will I use?',
12 | answer:
13 | 'You are only billed for successful patch installs. \
14 | This occurs when the user opens your app with the new patch installed. \
15 | A rule of thumb is number of patches per month times number of monthly active users. \
16 | If you have 1000 MAU and you ship 4 patches per month, you will likely use about 4000 patch installs.',
17 | },
18 | {
19 | question: 'Do you offer discounts?',
20 | answer:
21 | 'We offer committed use discounts for customers who commit to a certain number of patch installs per month. We offer committed usage discounts starting at 2.5M patches per month.',
22 | },
23 | {
24 | question: 'How much are your Enterprise plans?',
25 | answer:
26 | 'We offer our enterprise services starting at $2,000 per month. Below that level we recommend our self-service plans.',
27 | },
28 | {
29 | question: 'Do patch installs expire?',
30 | answer:
31 | 'Yes, patch install credits expire at the end of each billing period, typically one month. We do not offer rollover credits.',
32 | },
33 | {
34 | question: 'Can I pay annually?',
35 | answer: 'Yes, all paid plans support annual or monthly billing.',
36 | },
37 | {
38 | question: 'What payment methods do you accept?',
39 | answer:
40 | 'We accept any method of payment Stripe accepts in your region. Enterprise customers can also pay by invoice.',
41 | },
42 | {
43 | question: 'When am I charged for patch installs?',
44 | answer:
45 | 'At the start of each billing period, you are billed for your pre-paid patches. \
46 | In the case of a Pro plan, this includes 50,000 pre-paid patch installs. \
47 | "Overage" patch installs are billed at the end of each billing period. \
48 | The initial invoice (month 1) will only include the prepaid patches, however successive months will include \
49 | overage bills as well. For example, if you are using the Pro plan \
50 | (includes 50,000 pre-paid patches), and you use 100,000 patch installs each month, \
51 | you will be charged $20 when you sign up, and then $40 at the beginning of month 2 \
52 | ($20 for the 50,000 overage, and $20 for Month 2\'s Pro plan). \
53 | You can always check the status of your account and billing at \
54 | https://console.shorebird.dev/account.',
55 | },
56 | ];
57 |
58 | function PricingFaq() {
59 | return (
60 |
61 | {faqs.map((faq, index) => (
62 |
63 | {faq.question}
64 |
65 |
66 |
67 |
68 | ))}
69 |
70 | );
71 | }
72 |
73 | export { PricingFaq };
74 |
--------------------------------------------------------------------------------
/src/content/blog/patch-signing-beta.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Patch Signing Beta
3 | author: bryanoltman
4 | description: Announcing Patch Signing for Shorebird Code Push.
5 | date: 2024-06-05
6 | cover: patch-signing-cover.png
7 | ---
8 |
9 | Shorebird’s code push allows developers to update their Flutter apps instantly,
10 | over the air, deploying fixes directly to end users’ devices. Our solution takes
11 | less than 5 minutes to integrate and requires no code changes. Shorebird’s code
12 | push can update any Dart code in your app and we’ve designed the system to
13 | comply with Apple and Google store policies without sacrificing performance
14 | (even after patching).
15 |
16 | One of our goals is that Shorebird should be the default for all Flutter users.
17 | To do that, using Shorebird needs to be a strict upgrade from default Flutter.
18 | This includes ensuring that Shorebird is always helping with the security and
19 | privacy of your application.
20 |
21 | Today we're announcing another layer of security for Shorebird: patch signing.
22 | Patch signing allows you to cryptographically sign updates to your app and make
23 | your app require that patch contents are verified (via cryptographic signature)
24 | before applying the patch.
25 |
26 | This uses the same signing technologies that are used when distributing your app
27 | through the app stores. With patch signing, your app has the ability to
28 | independently verify patch contents without trusting any system or networks
29 | (including Shorebird) that might have been involved in transporting the patch
30 | from you to your users.
31 |
32 | Patch signing is an optional addition to the many ways in which Shorebird
33 | already works to protect the security of all our customers. We always take many
34 | precautions to protect the security of your app, including limiting what data
35 | leaves your servers (we never see or store your source code), securing what data
36 | we do store both via encryption in transit and in rest, cryptographically
37 | hashing and validating the contents of any patch you create, as examples. You
38 | can see a full breakdown of security practices we follow on your behalf in our
39 | [public security policies](https://handbook.shorebird.dev/security).
40 |
41 | The patch signing we’ve shipped today is marked as “beta”. The feature is fully
42 | functional, but we expect there to be rough edges in how the patch signing
43 | integrates with your existing developer flows. A system is only as secure as its
44 | weakest link, so improving our integrations with your preferred key management
45 | systems, etc. is where we go next and where we need your help.
46 |
47 | We’re looking for companies to work with us in testing and improving patch
48 | signing over the next few weeks. If you are interested, please give it a try:
49 | https://docs.shorebird.dev/guides/patch-signing/ You can also reach out to us
50 | via [GitHub](https://github.com/shorebirdtech/shorebird/),
51 | [Discord](https://discord.gg/shorebird) or [email](contact@shorebird.dev) should
52 | you have feedback or questions.
53 |
54 | We’d love to help you integrate Shorebird code push into your application.
55 | Please [reach out](mail:contact@shorebird.dev) to us if you have any questions
56 | or need help getting started.
57 |
58 | If you're curious about what we had to change in Dart to make this all possible,
59 | check out our [previous post](how-we-built-code-push).
60 |
--------------------------------------------------------------------------------
/src/content/success-stories/easyspend.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: EasySpend
3 | description:
4 | Next generation fintech companies turn to cloud services like Shorebird to
5 | help them easily deploy and stay up to date across all of their platforms.
6 | date: 2025-03-07
7 | cover: easyspend-cover.png
8 | highlights: ['Over 1,000 monthly active users']
9 | ---
10 |
11 |
12 |
13 | EasySpend is a next-generation fintech company based in Lagos, Nigeria, with a
14 | mission to transform financial transactions for individuals and businesses.
15 | Offering a suite of services including virtual cards, bill payments, and
16 | seamless NGN-USD transactions, EasySpend is solving some of Africa’s biggest
17 | financial challenges. From providing reliable virtual dollar cards for
18 | freelancers and remote workers to enabling businesses with bulk payment
19 | solutions, EasySpend is redefining how people move money.
20 |
21 | In creating the mobile applications for EasySpend they turned to Flutter to
22 | ensure that their customer base of over 100,000 active users have a consistent
23 | experience no matter what device they are using. For many Flutter developers,
24 | targeting multiple platforms is a key advantage of the framework. However,
25 | building and deploying iOS apps typically requires access to macOS, creating a
26 | barrier for developers who don’t own a Mac. This was the challenge faced by the
27 | team at EasySpend.
28 |
29 | > Being able to deploy to iOS without all of our developers using Mac’s removes
30 | > a significant hurdle for many developers like us
31 | >
32 | > - David Sylvester-Paul, CTO at EasySpend
33 |
34 | ## A Fully Remote Flutter Workflow
35 |
36 | By using services including Shorebird, David Sylvester-Paul, CTO at EasySpend,
37 | and his team have been able to deploy their Flutter application to iOS devices
38 | without all developers on their team owning a Mac. By leveraging Shorebird’s
39 | capabilities alongside other cloud-based tools, they bypassed the traditional
40 | Apple development constraints and successfully shipped their app across all the
41 | platforms that their customers are using.
42 |
43 | ## Seamless Multi-Platform Deployment
44 |
45 | By spending the engineering effort to integrate Codemagic with Shorebird they
46 | were able to create a mobile CI/CD pipeline that automatically pushes new
47 | builds, delivers patches, and significantly reduces deployment time. With all of
48 | this they have the flexibility to push out app changes on their schedule to
49 | ensure they are hitting their business objectives and customer needs.
50 |
51 | > In the past, we often wondered how other highly rated mobile apps updated
52 | > their features without forcing users to manually download an update from the
53 | > store. That curiosity led us to Shorebird, and ever since, we have implemented
54 | > it in all of our applications
55 | >
56 | > - David Sylvester-Paul, CTO at EasySpend
57 |
58 | With this approach, EasySpend supports multiple platforms—including iOS and
59 | Android—without over investing in cost prohibitive Apple hardware for an entire
60 | development team. This not only reduces development costs but also empowers more
61 | developers worldwide to build and distribute apps freely.
62 |
63 | > Shorebird made the process seamless, allowing me to focus on building great
64 | > apps rather than worrying about hardware limitations.
65 | >
66 | > - David Sylvester-Paul, CTO at EasySpend
67 |
--------------------------------------------------------------------------------
/src/content/blog/growing.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Expanding the Shorebird Team
3 | author: eseidel
4 | description:
5 | A quick look back to see how we got to today and how we are building for
6 | tomorrow.
7 | date: 2025-08-27
8 | cover: 'growing-cover.png'
9 | slug: 'shorebird-is-growing'
10 | ---
11 |
12 |
13 |
14 | 11 years ago, a group of us left the Chrome team believing there had to be
15 | something better than janky web pages, or complicated Java apps to build for
16 | mobile, and began
17 | [the journey that would yield Flutter](https://www.youtube.com/watch?v=xqGAC5QCYuQ).
18 | I would come to lead and grow the Flutter (and eventually Dart) teams at Google
19 | until leaving in 2022 to start Shorebird. I left Google in part because I
20 | realized there were problems I wanted to solve for Flutter that couldn't be
21 | solved within Google and felt that in the long-term Flutter would be best served
22 | by a company wholly focused on Flutter. I set out to build that company.
23 |
24 | Flutter over those 11 years has thrived. It saw early public success with the
25 | Hamilton App, NuBank, Toyota, Tencent, Alibaba, ByteDance, and Google's wide
26 | deployments across Assistant, GPay, Classroom, Earth, and more. Flutter now
27 | accounts for
28 | [almost a 3rd of all free app submissions on iOS](https://developers.googleblog.com/en/celebrating-flutters-production-era/)
29 | and is used around the globe by millions of developers and businesses of
30 | [all shapes and sizes](https://flutter.dev/showcase).
31 |
32 | Shorebird, has also found its place in this success. We started with Code Push,
33 | to address the
34 | [#1 most up-voted issue](https://github.com/flutter/flutter/issues/14330) on
35 | Flutter, and are now serving thousands of businesses globally each month,
36 | helping them update their apps for millions of customers. But there is so much
37 | more to do, and so much more we can do, to further Flutter and I still believe a
38 | focused home for Flutter is what lies in our future.
39 |
40 | Shorebird's revenues have tripled since the start of this year, and our userbase
41 | has grown similarly. So much so that our tiny team now struggles to keep up with
42 | it all. We're even about to launch a
43 | [second product](https://docs.shorebird.dev/ci), which surely will stretch our
44 | team thinner. It's time for Shorebird to grow. We're well funded from a top-5 VC
45 | and excellent angel investors and on a path to cross into profitability early
46 | next year. But we're still small enough (only 4 of us!) that there is vast
47 | amounts of opportunity available to anyone joining us to chart the future of
48 | Shorebird and Flutter.
49 |
50 | We're hiring for a range of engineering roles, including a web-specialist
51 | (including potentially early-career candidates), a senior full-stack/generalist
52 | and a senior C++ specialist (to own our custom compiler and runtime). We're also
53 | hiring someone to lead our marketing efforts and teach this group of engineers
54 | how to get the attention of the millions of Flutter developers who haven't even
55 | heard of us yet. We're fully remote, able to hire anywhere in North America with
56 | existing team members near San Francisco, Chicago and New York City. We pay well
57 | (including a large equity stake), with good benefits and are looking for great
58 | folks like yourself to join us.
59 |
60 | Come work with us and build the future of development!
61 |
62 | https://shorebird.dev/jobs
63 |
--------------------------------------------------------------------------------
/src/content/blog/tracks-percentage-rollouts-a-b-testing.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Tracks, Percentage Rollouts and A/B testing
3 | author: eseidel
4 | description: Announcing Tracks, Percentage Rollouts and A/B testing
5 | date: 2024-11-14
6 | cover: tracks-cover.png
7 | ---
8 |
9 | Building on the success of our brand-new
10 | [`shorebird_code_push` package](https://pub.dev/packages/shorebird_code_push/versions/2.0.0)
11 | 2.0, we're announcing patch tracks, which can be used to support
12 | percentage-based rollouts and A/B testing within Shorebird.
13 |
14 | The `shorebird_code_push` package is a completely optional package that allows
15 | developers to customize the user experience of downloading and installing
16 | over-the-air updates with Shorebird. It was built for teams that want more
17 | control over when updates are downloaded and which users receive those updates.
18 |
19 | Shorebird strongly believes in user privacy, and we never collect any
20 | information from our customer's customers. This means that we can't tell one of
21 | your customers apart from another. This has previously prevented us from being
22 | able to offer patch rollout options that target specific users.
23 |
24 | However, with the updated package:shorebird_code_push, we've provided the API
25 | tools to make it easy for you to provide your own group-based control over who
26 | gets what updates when. With patch tracks, you can support QA testing, a public
27 | beta, or even for controlled percentage-based rollout across your userbase.
28 |
29 | `ShorebirdUpdater` methods `checkForUpdate` and `update` now take an optional
30 | `track` parameter which affords you powerful control over app updates in the
31 | field.
32 |
33 | Examples of features it is now possible for you to add to your process:
34 |
35 | ### Group based update distribution
36 |
37 | The `shorebird` command line now takes a `--track` parameter which allows you to
38 | specify the track to send a patch to. For example, you can use
39 | `shorebird patch ios --track staging` to submit a patch to your iOS builds which
40 | is only available when requesting updates to the `staging` track.
41 |
42 | This can be used for example to distribute updates only to your QA team for
43 | testing, which you can then later promote to the `stable` track for distribution
44 | to all users.
45 |
46 | ### Percentage Rollouts
47 |
48 | Similar to groups, it is now possible to implement percentage rollouts of
49 | patches with Shorebird. Currently we do not provide UI for controlling rollouts,
50 | but rather the tools to allow customers to do so on their own. We've written a
51 | guide demonstrating how this can be accomplished:
52 | https://docs.shorebird.dev/guides/percentage-based-rollouts/
53 |
54 | ### A/B Testing
55 |
56 | These same track APIs are also able to support A/B testing.
57 |
58 | The logic is very similar to a percentage based rollout above, just determining
59 | whether to use patch A or B based on some other criteria.
60 |
61 | ## Get Started
62 |
63 | You can try out the new version now by adjusting your `pubspec.yaml` to use
64 | version 2.0 of `shorebird_code_push` and re-releasing a new version of your
65 | application using the revision of Flutter 3.24.5.
66 |
67 | ```yaml
68 | dependencies:
69 | shorebird_code_push: ^2.0.0
70 | ```
71 |
72 | We'd love to hear your feedback! If there's anything you'd like to see adjusted
73 | or improved, please
74 | [let us know by filing an issue](https://github.com/shorebirdtech/updater/issues/new).
75 |
--------------------------------------------------------------------------------
/src/components/pricing/pricing-calculator.tsx:
--------------------------------------------------------------------------------
1 | import { Button } from '@/components/ui/button';
2 | import { Card, CardContent, CardHeader } from '@/components/ui/card';
3 | import { Slider } from '@/components/ui/slider';
4 | import { ArrowRightIcon } from '@phosphor-icons/react';
5 | import React from 'react';
6 |
7 | const clamp = (n: number, min: number, max: number) =>
8 | Math.min(Math.max(n, min), max);
9 |
10 | function PricingCalculator({ hideCTA }: { hideCTA?: boolean }) {
11 | const [activeUsers, setActiveUsers] = React.useState(5000);
12 |
13 | const calculatePrice = () => {
14 | const totalPatches = 1 * activeUsers; // Assume 1 patch per active user
15 | const plan = totalPatches > 5000 ? 'Pro' : 'Free';
16 | const platformFee = totalPatches > 5000 ? 20 : 0;
17 | const includedPatchInstalls = plan === 'Pro' ? 50000 : 5000;
18 | const overages = clamp(
19 | Math.ceil((totalPatches - includedPatchInstalls) * (1 / 2500)),
20 | 0,
21 | Infinity,
22 | );
23 |
24 | return {
25 | total:
26 | activeUsers > 2000000
27 | ? null
28 | : `$${(platformFee + overages).toLocaleString()}`,
29 | };
30 | };
31 | const pricing = calculatePrice();
32 | const monthlyActiveUsers =
33 | activeUsers > 2000000 ? '2,000,000+' : activeUsers.toLocaleString();
34 |
35 | return (
36 |
37 |
38 |
54 |
55 |
56 |
57 |
58 | Users
59 |
60 | {monthlyActiveUsers}
61 |
62 |
63 |
64 | Estimated Cost
65 |
66 | {pricing.total ?? 'Contact Us '}
67 |
68 |
69 |
71 | setActiveUsers(value as number)}
77 | />
78 |
79 |
80 |
81 | *Prices are quoted in USD and sold as "patch installs per month",
82 | reflecting successful installs of a given patch. For example, 1
83 | patch pushed to 10 devices is 10 installs. 2 patches pushed to 5
84 | devices is also 10 installs.
85 |
86 |
41 | Success stories
42 |
43 |
44 |
57 |
58 |
85 |
86 |
87 |
88 |
89 |
--------------------------------------------------------------------------------
|