Discovery and scope
We discuss the audience, product goals, launch window, and existing systems. Agree on a prioritized scope and how we will tell when a milestone is complete.
Independent app developer · Made in Germany
See how we can take your app from the first conversation through design, milestone reviews, device testing, and release.
Tell Me About Your AppStart with what matters
You can start with a short description of your idea, your users, and what you want the first version to accomplish. The process is designed to make product decisions visible as the project moves from scope through launch.
Discuss your first releaseKnow what you are paying for
We agree on a first-release scope. I turn the design into a clickable prototype you can open on your phone. The first payment falls due once that prototype is completed, according to the written proposal. Only then do we proceed with developing the actual app and integrations.
A clickable prototype demonstrates navigation and screen design; it is not yet a live app with working payments, accounts, or backend features.
The practical details
Each project starts with the problem, audience, and desired outcome. Scope and milestones are agreed before implementation. During development, working builds provide a practical basis for feedback, and release preparation includes the accounts, assets, and documentation required for handoff.
We discuss the audience, product goals, launch window, and existing systems. Agree on a prioritized scope and how we will tell when a milestone is complete.
Use a prototype to check navigation before coding. Review working builds as milestones are reached, using Central Time meeting windows for decisions and asynchronous feedback between demos.
Test the release candidate on real devices. Review store requirements and hand over build, configuration, and release documentation.
Planning notes
Tell me what you want to build, who will use it, and what you want the first version to accomplish. I’ll ask about your priorities, timeline, and any existing tools or systems. From there we can define the scope and milestones for your project.
During design and development, you can review screens and working builds. Clear feedback at each milestone helps us make decisions while the product is taking shape. We can coordinate by email and schedule video calls during shared working hours.
Before launch, we’ll review the agreed user journeys on relevant devices and prepare the materials needed for release. Handoff can include the build and configuration instructions your team needs to continue working with the product.
Your first release
The scope discussion covers the user journey, platforms, existing systems, and constraints. We can then identify open questions and decide what needs to be resolved before a written project-specific offer.
Before launch
You can review screens during design and test working builds during development. Feedback is most actionable when it points to a specific step, device, expected result, and what actually happened.
Project investment
The proposal depends on the agreed scope and assumptions. Changes to features, integrations, or release requirements can affect effort, so we’ll discuss those changes as they arise.
Explore the USD estimatorAfter the build
Before launch, we’ll review release responsibilities, account access, configuration, and the agreed documentation. Further updates or maintenance can be discussed for the period after the first release.
A closer look
A clear process gives you opportunities to review the product before release. The exact activities and deliverables are agreed for your project and its current stage.
We discuss your audience, business goal, the core workflow, and any existing designs or systems. We identify the essential features and the open questions that affect an estimate.
The resulting proposal can describe the agreed work, milestones, assumptions, and responsibilities. If the scope changes, we discuss the effect before adding work.
User flows and screen designs make the intended experience visible early. Depending on the project, you can review a clickable prototype before full implementation.
During development, working builds give you a chance to test real interactions on your devices. Feedback is most useful when it identifies the task, expected result, and what actually happened.
Before launch, we review the agreed user journeys, integrations, and platform-specific behavior. Store accounts and submission materials need to be ready for the release.
I can help with store submission and provide agreed build and configuration documentation. Further improvements or support can be scoped around your priorities after launch.
Common questions
If you’re unsure about the scope, budget, or process, these answers can help you plan the next step.
We can exchange written updates and test builds between meetings, then schedule Zoom or Microsoft Teams calls during overlapping hours in Central Time and Germany.
A short description of the users, problem, core workflow, existing systems, and intended timeline is enough to begin a scope discussion.
Yes. Project discussions, written updates, and scheduled Zoom or Microsoft Teams calls can take place in English.
You can review screens and try working builds as agreed milestones are reached, then share feedback on the relevant workflows.
Tell me who the app is for, what users need to do, any existing systems, and your expected timeline or budget if known.