How long does it take to build a mobile app?

Most MVPs take 4-8 weeks from kickoff to launch. More complex apps with integrations, custom backends, or compliance requirements typically take 14-20 weeks. We'll give you a realistic timeline during our initial consultation — we don't overpromise to win the deal.

How much does mobile app development cost?

We offer competitive European rates without compromising on quality: Simple apps (basic features, single platform): ~$9,360 – $17,550 Medium complexity (user accounts, payments, API integrations): ~$17,550 – $40,950 Complex apps (real-time features, multiple integrations, admin dashboards): ~$40,950 – $70,200 Enterprise solutions (compliance requirements, advanced security, legacy system integration): $70,200+ We provide detailed fixed-price quotes after understanding your requirements, no surprises in the middle of the project. With 13+ years of experience and 300+ delivered projects, we know how to scope accurately.

Do you build for both iOS and Android?

Yes. We typically use cross-platform frameworks like React Native or Flutter, which let us build for both platforms simultaneously. This reduces cost and development time by 30-40% compared to building two separate native apps.

What industries do you work with?

We don't specialize in one industry. Over the past 13 years we've built apps for e-commerce stores, SaaS startups, HR companies, hotels, B2B platforms, and more. If you need a mobile app, a web platform, or custom software that actually works in production, we can probably help. The common thread is clients who need reliable delivery, not the cheapest quote.

What does your development process look like?

We work in 2-week sprints. At the end of each sprint, you see working software, not slides or mockups. You'll have a dedicated point of contact, access to our project management tools, and bi-weekly demo calls. No disappearing for months and hoping for the best.

Will I own the source code?

Yes, 100%. You own everything we build including source code, documentation, designs, deployment configurations. No licensing fees, no lock-in. If you want to take the code to another team tomorrow, you can.

How do you handle communication?

You'll have direct access to the engineers working on your project and not just a project manager relaying messages. We use Slack for day-to-day communication and scheduled video calls for demos and planning. Most questions get answered within a few hours during business hours.

What if I need changes after launch?

We offer ongoing support and maintenance packages, but you're not locked in. Since you own the code and we document everything, any competent development team can pick up where we left off.

What technologies do you use?

Mobile:React Native, Flutter, Swift (iOS), Kotlin (Android), Unity Engine and sometimes just WebView Web: PHP ,React, Next.js, Node.js, Python Backend: AWS, Google Cloud, PostgreSQL, MongoDB We choose the stack based on your needs, not what's trendy. We'll recommend what makes sense for your timeline, budget, and long-term maintenance.

Can you work with our existing codebase?

Yes. We regularly take over projects from other teams. We'll start with a code audit to assess what's salvageable and what needs rebuilding. We'll be honest sometimes it's faster to rebuild than to fix.

Do you handle UI/UX design?

Yes. Our design team handles user research, wireframes, prototypes, and final UI design. Good design isn't optional apps that look dated or are hard to use don't get traction, no matter how solid the code is.

How do you ensure app security?

Security is built into our process, not bolted on at the end. We use encryption for data at rest and in transit, secure authentication, and follow OWASP guidelines. For healthcare or financial apps, we can implement HIPAA or PCI-DSS or WCAG or GDPR compliance requirements.

How do I know if we're a good fit?

We work best with clients who: - Have a clear business problem they're trying to solve - Are ready to invest in quality (not looking for the cheapest option) - Want to be involved in the process, not just hand off requirements and disappear - Need software that works reliably in production

What do you need from me to get started?

For an initial consultation, just a rough idea of what you want to build and your goals. We'll ask questions to fill in the gaps. For a formal proposal, we'll need more detail but we'll guide you through that process.

How do I get a quote?

[Contact us](/contact) with a brief description of your project. We'll schedule a 30-minute call to understand your needs, then follow up with a detailed proposal within 3-5 business days.

What if I'm not happy with the work?

We demo working software every two weeks. If something isn't right, we catch it early and fix it not three months later when it's expensive to change. If there's ever a fundamental disagreement, you own the code and can walk away.

What if my requirements change mid-project?

They will, that's normal. Our sprint-based process is designed for this. We'll discuss the impact on timeline and budget, and you decide whether to proceed. No change requests disappear into a black hole.

What happens if a key team member leaves?

We have engineering teams across multiple locations and other regions, so there's always someone ready to step in. We document everything properly and use standard code practices, so knowledge doesn't get stuck in one person's head. In 13 years, we've never had a project stall because of team changes.

How does pricing work?

We offer two models: 1) Fixed-price projects: Best for well-defined scopes. You know the total cost upfront. 2) Time & materials: Best for evolving projects. You pay for actual hours worked, with full transparency. Most clients start with fixed-price for the MVP, then move to time & materials for ongoing development.

What are your payment terms?

Typically 30-40% upfront, with remaining payments tied to milestones. We don't ask for 100% upfront, and we don't invoice for work you haven't seen.

Do you offer payment plans?

Yes. We can structure payments across the project timeline to help with cash flow. Let's discuss what works for your situation.

Favicon Checker 2026 | free by FQB

See Why Your Icon Is Missing

Is your favicon perfect? This free favicon checker validates more than a dozen settings to make sure your icon works correctly on all major platforms — browsers, iOS, Android, Google Search, and Windows. Enter your URL, run the check, and get a clear pass/fail for every file that matters.

Run the Favicon Check Generate Missing Files

Is my favicon.ico correct?

Every browser still auto-requests /favicon.ico from your root, even if you never added a <link> tag for it. If this file is missing or returns a 4xx error, browsers fall back to a blank icon — and some will log a console error on every page load.

Common favicon.ico problems the checker catches:

File not found (404). The file does not exist at /favicon.ico. Upload one to the server root.
Wrong Content-Type header. The server serves the file with an incorrect MIME type. It should be image/x-icon or image/vnd.microsoft.icon.
Blocked by robots.txt. If /favicon.ico is disallowed, Googlebot and other crawlers cannot fetch it. Check your robots.txt and remove any rule that blocks the path.
File too small. A 16×16 ICO is technically valid but looks blurry on HiDPI displays. Use a 256×256 ICO for best results across all contexts.

Fix: Place a 256×256 favicon.ico at your site root and add <link rel="shortcut icon" href="/favicon.ico"> to your <head>.

Will my favicon appear on iOS?

When a user adds your website to their iPhone or iPad home screen, iOS looks for apple-touch-icon.png. This is separate from your browser favicon. If the file is missing, iOS generates a blurry screenshot of your page instead of showing a clean icon.

What the checker validates for iOS:

apple-touch-icon.png exists at the expected path (usually /favicons/apple-touch-icon.png or /apple-touch-icon.png).
The <link> tag is present in your HTML: <link rel="apple-touch-icon" sizes="180x180" href="/favicons/apple-touch-icon.png">.
Correct size. Apple requires exactly 180×180 pixels. Smaller images are upscaled and appear blurry.

Note: Do not add rounded corners or transparency to your apple-touch-icon. iOS applies its own corner mask and shadow automatically. Provide a clean, full-bleed square image.

Is my favicon ready for Google Search results?

Google displays your favicon in the search results next to your page title and URL. When it’s missing, your listing looks unbranded and earns less trust. Google has specific requirements that many sites fail silently:

Minimum size: 48×48 pixels. Google ignores icons smaller than 48px. A 16×16 PNG or a tiny ICO won’t be shown. The icon must also be a multiple of 48px in size.
Publicly accessible. The icon URL must return a 200 response with no authentication, no redirect loop, and no CORS restriction. Googlebot must be able to fetch it directly.
Not blocked by robots.txt. Add Allow: /favicon.ico and Allow: /favicons/ if those paths are covered by a broader Disallow rule.
Correct HTML tag. Google reads the <link rel="icon"> tag in your page’s <head>. If the tag is absent it falls back to /favicon.ico.
Square aspect ratio. Google crops non-square icons to a circle. Use a square image to control how it looks after cropping.

After fixing your favicon, go to Google Search Console → URL Inspection → Request Indexing on your homepage. It typically takes 24–72 hours to appear, and up to a week for the favicon cache to update.

Are my PNG favicons valid?

Modern browsers prefer PNG over ICO for crisp rendering, especially on HiDPI and Retina screens. The checker verifies the three raster sizes that cover all major browser contexts:

16×16 px — Standard browser tab. Used by older browsers and some system contexts.
32×32 px — Windows taskbar, pinned sites, and high-DPI tabs.
48×48 px — Desktop shortcuts and the minimum size accepted by Google Search.

Each file should be correctly linked in your HTML with its corresponding sizes attribute:

Does my Android and PWA icon work?

Android Chrome does not use the <link rel="icon"> tags for home screen icons. Instead it reads the manifest.webmanifest file. The checker validates:

favicon-192.png exists. This is the standard Android home screen icon. Linked from the manifest as a 192×192 icon.
favicon-512.png exists. Used for PWA splash screens and high-resolution contexts. Required for "Add to Home Screen" prompts on Android.
manifest.webmanifest is reachable. The manifest must be linked via <link rel="manifest"> and must return a valid JSON response.

Tip: The icon paths inside the manifest are relative to the manifest file itself. If your manifest is at /favicons/manifest.webmanifest, then "src": "favicon-192.png" resolves to /favicons/favicon-192.png.

Is my SVG favicon set up correctly?

SVG favicons are the modern standard supported by Chrome, Firefox, Edge, Opera, and Safari 15+. They render crisply at any resolution and can respond to dark mode via CSS media queries embedded in the SVG. The checker confirms whether your SVG icon is reachable and correctly linked:

<link rel="icon" type="image/svg+xml" href="/favicons/favicon.svg">

The SVG favicon is not critical for site function — browsers fall back to ICO or PNG gracefully — but it is the cleanest solution for modern browsers and eliminates pixelation at all zoom levels.

Favicon Checker: Quick Fix Reference

favicon.ico missing → Upload a 256×256 ICO to /
favicon.png missing → Upload a 96×96 PNG to /
PNG sizes missing → Upload 16, 32, 48px PNGs to /favicons/
apple-touch-icon missing → Upload a 180×180 PNG to /favicons/
favicon-192.png missing → Upload 192×192 PNG and check your manifest path
favicon-512.png missing → Upload 512×512 PNG and check your manifest path
Favicon not in Google → Check robots.txt, ensure 48px+ size, request re-indexing in Search Console