Developers for Svelte and SvelteKit apps

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers who work on Svelte and SvelteKit apps, matched to your work, so you choose who joins your team.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

How hiring works

From the first call to their first day, you decide each step.

  1. You tell us.

    Tell us about the work

    A short call about your app, its pages and components, how it’s built and run, and who you need. The first call is free.

  2. We introduce.

    Meet developers matched to it

    Within 48 hours, we introduce developers whose experience fits, with the work each has done.

  3. You choose.

    Choose who joins

    You talk to each one and decide who starts.

  4. They start.

    Start on a date you agree

    They join your team in your tools, and work in your time zone.

What they work on

Components, upgrades, pages and the checks around them.

New features

Components and pages added to your app, with tests from the start.

Svelte 5, a component at a time

Components moved to the new syntax while the rest keep running.

SvelteKit 3

The app moved from its latest 2.x release, with the deprecation warnings cleared first.

Pages made the way each needs

Built ahead of time, made on each visit or in the browser, set page by page.

Forms that work before the scripts load

Form actions that still send, then improve once the scripts arrive.

Performance, measured first

Each change measured before and after, on the pages your users open most.

Checks in CI

The type check, tests and the compiler’s accessibility warnings on every change.

Planning a new app, or a bigger move? Development for Svelte and SvelteKit apps

Ways to hire

One developer

Full time, by the month, working as part of your team.

A small team

Developers who work on your app together, from the move to the new syntax and the page options to the forms and the checks in CI.

How each is paid for: PricingWhen each way of working fits: Engagement Models

Working in your team

They work the way your team already does.

  • Your tools. Your own chat, tickets and code repository, so you see the work as it happens.
  • Your hours. They work in your time zone, on hours you agree before anyone starts.
  • Your access. You decide what they can reach, and remove it when they leave.

Tell us who you need

A few details are enough to start. We’ll reply by email to arrange a short call.

What should they work on?

{{ eWork }}

How many developers?

{{ eDevs }}

When should they start?

{{ eStart }}

{{ eHName }}

{{ eHMail }}

{{ eHSend }}

{{ hireThanks }}

We’ll be in touch by email, and introduce developers matched to your request within 48 hours.

Questions worth asking

How soon can a developer start?

We introduce developers matched to your work within 48 hours. Once you’ve chosen, they start on a date you agree.

Can we interview them first?

Yes. You talk to each developer and choose who joins.

Will they work in our time zone?

Yes. They work in your time zone, on hours you agree before anyone starts.

What does it cost?

It depends on the experience you need and how long you need them. Your proposal sets out the monthly fee and how you pay before anyone starts.

Pricing

Can they move our components to Svelte 5 without stopping other work?

Yes. Because Svelte 5 still runs the older syntax, they can move one component at a time, with its tests, while the rest of the app keeps working.

Can they take our app to SvelteKit 3?

Yes. They move it to the latest SvelteKit 2 release first and clear its deprecation warnings, then run the migration tool on a branch and finish what it lists, with the tests passing.

Can they work on the component library our apps share?

Yes. They add to it and package it, with tests for each component, and publish each new version for your apps to take up when they’re ready.

Can you take on the whole project instead?

Yes. That starts with a written review of your app, its components and routes, its tests and the way it’s built and deployed, and a proposal for a first step, such as the latest SvelteKit 2 release in place on a branch.

Development for Svelte and SvelteKit apps

Webair is independent of the Svelte project, and isn’t sponsored by, endorsed by or affiliated with it.

Let’s build it better

Tell us about your app and the work ahead, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}