DylTecIndependent software studio · Dubuque, Iowa

Websites · Mobile apps · Business software

Thoughtfully designed. Built for your business.

I design, build, and look after custom websites, mobile apps, and business software — one developer, working directly with you from the first question through launch and after.

Start a project Explore selected work

Based in Dubuque. Serving Iowa. Remote projects welcome nationwide.

WebsitesMobile appsBusiness softwareDesigned, built, and looked after.

What do you need?

Three kinds of work.
One careful standard.

Most projects start as a plain question: this part of the business has outgrown its current tools — what would it take to fix that? The answers below are the shapes the work usually takes.

A website

A clear site that explains what you do, earns the next conversation, and stays easy to keep current.

Useful when customers need to understand you before they ever call.

A mobile app

A phone app built around the thing people already come to you for — close at hand, not buried behind a link.

Useful when the moment matters on a phone: listening, checking, approving.

Business software

Custom tools for the work behind the scenes — intake, inventory, handoffs, and the details that outgrow spreadsheets and clipboards.

Useful when the workflow is yours specifically, and no packaged product quite fits it.
Start a project

Not sure which one it is? That is a normal place to start.

Selected work

Different challenges.
Considered solutions.

A radio station and a disaster-relief nonprofit. Two different workflows, each with software built around the people using it. Client names remain private.

Radio · Mobile listening app

A station, closer to its listeners.

A local radio station. Name withheld.

An existing station stream, easier to reach on the phone. Live listening, a show clock, and lock-screen playback in one mobile app.

The problem
Listeners needed an easier way to reach the station’s existing live stream on their phones. The old path was a buried URL.
What I built
  • A phone app for the live stream, the show clock, and a way to keep the station on the lock screen.
Scope
This is one small station using an existing stream. The published scope is a mobile listening app: live listening, a show clock, and lock-screen playback. This project did not include a website. Additional platforms or features need their own scope.
Read the project story

Open the station, not a buried URL

The listening app puts the live stream and show clock together. Lock-screen listening keeps the station close at hand rather than asking listeners to find the old link again.

Keep listening close at hand

Lock-screen playback lets listeners continue with the station without reopening the app. The project was focused on the mobile listening experience, not a station website.

Care after launch

Ongoing care keeps the mobile app supported as the station’s stream and listening needs change.

Why it stays unnamed

The name stays off this page to respect the station’s privacy. This case study describes the workflow and scope without identifying the client.

Read the full case study

Illustrative mobile interfaces — not client screenshots.

Nonprofit · Warehouse & donation inventory

Clarity on the warehouse floor.

A disaster-relief nonprofit. Name withheld.

A warehouse screen and dock phone screens for donated goods, intake, and handoffs that had outgrown clipboards.

The problem
Intake, inventory, and handoff had outgrown clipboards. The floor still has to show bins, a donation lot, and the one exception that cannot wait until morning.
What I built
  • The warehouse floor as a screen: bins, a donation lot, and exceptions that stay visible.
  • Phone faces for the dock — scan a lot, hold a cold chain, keep a missing photo from moving product.
Scope
This is a client-specific workflow for physical donations: intake, inventory, and dock handoffs. It is custom project work rather than a ready-made warehouse product. Another organization’s connectivity, integrations, and reporting needs would be scoped separately.
Read the project story

See the lot and the warehouse floor

Bins, a donation lot, and exceptions share a warehouse view. The screen makes the work visible instead of leaving the next person to find the right clipboard.

Keep exceptions with the dock work

Phone screens support scanning a lot, holding a cold chain, and keeping a missing photo from moving product. A hold needs to be visible when someone takes the next step, including across shifts.

Care after launch

The month covers hosting, updates, support, and ongoing features as the warehouse changes.

Why it stays unnamed

I keep the nonprofit unnamed because the warehouse is still theirs to talk about, not mine to advertise.

Read the full case study

Illustrative interfaces — not client screenshots.

How I work

Four steps, plainly.

Clear scope, close collaboration, and care that continues after launch. You know who is doing the work and what comes next.

Understand

We talk through the work itself: what you do now, what is getting in the way, and who needs to use what I build.

Define

The scope is written down — what is included, what is not, what the build costs, and what ongoing care covers.

Build

I design and build the work, keeping you close to the decisions, so you see it taking shape rather than at the reveal.

Look after

Launch is not the end. Hosting, updates, support, and new features continue as your work changes — scoped so it stays clear.

The person you would work with

Dylan Schwering

  • Independent software studio
  • Dubuque, Iowa
  • Serving Iowa · Remote nationwide
  • Brand · DylTec

One developer. A direct working relationship.

I’m Dylan Schwering, based in Dubuque, Iowa. I build custom websites, mobile apps, and business software — designed, built, and looked after in one place.

When you work with DylTec, you work with me: no account layers, no handoff to a team you have not met. The person asking the careful questions is the person designing and building the work.

Based in Dubuque. Serving Iowa. Remote projects welcome nationwide.

Questions

Practical answers,
before we talk.

The things worth knowing up front: cost, distance, what happens after launch, and how a project starts.

What do builds cost?

The exact quote depends on scope. Every project is priced from the work it actually needs — there is no rate card and no package price.

A build is scoped and priced once. Ongoing care is scoped separately as its own arrangement. Tell me the problem and I can talk through what a realistic scope looks like.

Do you work remotely?

Yes. Based in Dubuque. Serving Iowa. Remote projects welcome nationwide. Either way, you work directly with me.

What happens after launch?

Care continues. Ongoing care covers hosting, updates, support, and new features as your work changes — the arrangement that keeps, for example, a station’s app current or a warehouse workflow supported.

It is scoped separately from the build so both sides stay clear about what is covered.

How does a project start?

With a short brief and a conversation. A useful first message names what you need, the problem it should solve, and — if you know them — budget and timing.

Starting a scope does not commit either of us.

Who would I work with?

Me, Dylan Schwering — one developer in Dubuque, Iowa. The person designing and building the work is the person you talk to.

Start a project

Tell me what you have in mind.

A few sentences is enough to begin. We will sort the rest out in a conversation — direct, unhurried, and with the same person who would build the work.

A useful first message

  • What you needA website, a phone app, software for the work behind the scenes — or simply the problem, in your own words.
  • The problem it should solveWhat is getting in the way today: a buried link, a clipboard that leaves with third shift, a spreadsheet that outgrew itself.
  • Budget and timing, if knownIf you know them, say them. If you do not, say that too — scope is worked out together.

Send me the short brief

This form comes straight to me. A sentence about the problem is enough to start.

What you need (required)
Budget band (required)

Leave an email or a phone number — either one is enough for me to write back.

I read this myself. What I keep from a brief.

Prefer to write directly?

support@dyltec.com(515) 298-2243
Direct, one-to-one, from Dubuque.