Screen and journey map
We define roles, main screens and features deliberately left out of the first release.
Build the first release around one real need.
We clarify why someone will open the app and build the first release around that journey.
What we plan together
From prototype to working product. A prototype may be enough to test an idea; accounts, stored data or notifications need a working first release.
Application and data layer
The interface, server connections and access controls are developed to the agreed scope.
Device testing and store preparation
We check core journeys, error states and screen sizes, then prepare the agreed submission requirements.
Scope matters
Payments, chat, maps and offline support are assessed separately. Store, hosting and usage fees are separate; store approval dates are not guaranteed.
From an idea to everyday use.
MealBuddy and Fırsat Kaşifi are our projects for two different needs. Let’s define the core job of your application, too.
Explore the product projects
What to bring to discovery
- The single main problem the app should solve
- Essential screens and user roles for the first release
- Existing APIs, design files and store account status, if available
Questions before we start
Is a clickable prototype a working app?
No. It demonstrates screens and interactions. Real data storage, accounts and server operations require separate development.
Can you target both iOS and Android?
We can assess a shared codebase against the required device features. Platform-specific requirements and separate native implementations can change the scope and cost.
Are store and server fees included?
Development, store and server costs are itemised in the proposal. You can use your own publisher accounts; suitable projects may also be considered for publishing and maintenance under Nolien Labs.
Which product projects can I see?
Explore MealBuddy and Fırsat Kaşifi. MealBuddy images show the running app in English; the Fırsat Kaşifi presentation includes illustrative UI. Follow the project links for current product details.
Can I publish my app under Nolien Labs?
For suitable projects, plan publishing and maintenance with shared infrastructure and one team. This can reduce the setup and management involved in a separate IT operation. Publisher accounts, branding, source-code rights, maintenance and future transfer terms are agreed before the proposal. Costs depend on scope.
Have a project in mind?
Tell us what you do, what needs to improve and what you already have. We will clarify the scope before proposing a solution.