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 Not Showing in Google? Fix It Fast!

Why Your Favicon Doesn’t Show in Google (and How to Fix It)

Stop generating dozens of favicon files for every possible size. Modern browsers have simplified things dramatically, and you only need a small set of well-chosen icons to ensure your site looks perfect across every platform and device.

Why Most Favicon Setups Are Overcomplicated

Traditional favicon generators output 20 or more files — a relic from an era when every browser and OS required its own specific format and resolution. Developers still ship these bloated icon sets out of habit, adding unnecessary weight to projects without any measurable benefit.

The truth is that browser support has converged. A lean, intentional favicon setup performs identically to one with dozens of redundant files, while being far easier to maintain.

Favicon Not Showing in Google? Start Here

If your favicon doesn’t show in Google search results, it’s usually one of these:

The icon isn’t accessible at the expected URL (check /favicon.png and /favicon.ico).
The page hasn’t been recrawled yet (use Search Console URL Inspection and request indexing).
The favicon is blocked by robots.txt or returns a 4xx/5xx status.
The HTML is missing the icon tags or the manifest path is wrong.

Run the checker below to confirm what Google can actually fetch, then generate the fixed set in one click.

The Favicon Files That Cover Every Platform (and where to put them)

Use this exact layout — it matches the generator and the checker on this page:

Open Favicon Generator Run Favicon Checker

/favicon.png — 96×96 PNG at the site root
/favicon.ico — 256×256 ICO at the site root
/favicons/favicon.svg — scalable vector icon with dark mode support
/favicons/favicon-16x16.png — small raster icon
/favicons/favicon-32x32.png — taskbar-sized raster icon
/favicons/favicon-48x48.png — desktop/high-DPI raster icon
/favicons/apple-touch-icon.png — 180×180 PNG for iOS home screen
/favicons/favicon-192.png — Android home screen icon (from the manifest)
/favicons/favicon-512.png — PWA splash screen icon (from the manifest)
/favicons/manifest.webmanifest — references the 192px and 512px icons for Android/PWA

1. favicon.png (96×96) — Root PNG

Browsers happily downscale this 96×96 PNG for tabs and pinned shortcuts. Keeping it at the root (/favicon.png) ensures every crawler and browser finds it instantly. Preview size kept small on purpose:

Preview:

2. favicon.ico (256×256) — Root Legacy Fallback

The ICO format keeps old browsers happy. Shipping a single 256×256 image inside the ICO covers high-res Windows contexts without bloating multiple embedded sizes.

Tip: Browsers still auto-request /favicon.ico. Keeping this file at the root with an explicit rel="icon" tag gives you cache control while satisfying legacy behavior.

3. favicon.svg — Scalable Favicon With Dark Mode Support

SVG favicons are the modern standard, supported by Chrome, Firefox, Edge, Opera, and Safari 15+. Because SVGs are vector-based, they render crisply at any tab size without pixelation. Even better, you can embed a CSS media query directly inside the SVG to switch colors for dark mode users.

Tip: The SVG icon is the preferred format for modern browsers. It scales perfectly at any resolution and can adapt to light/dark mode automatically via CSS media queries.

4. favicon-16/32/48.png — Raster Browser Icons

Some contexts still prefer explicit raster icons. Keep these PNGs inside /favicons/ so the HTML links stay organized while providing sharp results for tabs, taskbars, and desktop shortcuts.

5. apple-touch-icon.png — iOS and macOS Safari

When users add your website to their iPhone or iPad home screen, iOS uses the apple-touch-icon.png file. This must be a 180×180 pixel PNG. iOS automatically applies rounded corners and visual effects, so provide a clean square image without your own masking or rounded edges.

Tip: Leave approximately 20 pixels of padding around your logo within the 180×180 canvas. This safe area ensures the icon doesn't appear clipped after iOS applies its corner rounding and drop shadow effects.

6. manifest.webmanifest — The Web App Manifest

The manifest in /favicons/ tells Android Chrome where to find your PWA icons and what sizes are available. Paths are relative to the manifest file itself:

{
  "name": "Your Site",
  "short_name": "Site",
  "icons": [
    { "src": "favicon-192.png", "type": "image/png", "sizes": "192x192" },
    { "src": "favicon-512.png", "type": "image/png", "sizes": "512x512" }
  ],
  "start_url": "/",
  "display": "standalone",
  "theme_color": "#ffffff",
  "background_color": "#ffffff"
}

Complete HTML Favicon Markup

Add these lines inside your HTML head section and you're done:

Root pair + eight files in /favicons/. Full favicon coverage on every major browser and device.

Favicon Sizes You Can Safely Skip

Many older tutorials recommend additional sizes. Once you ship the set above, you can skip the rest:

128×128, 144×144 — Legacy for Chrome Web Store/Windows 8 tiles; modern browsers scale from 96px or the ICO.
Extra-large PNGs (256×256, 384×384) — Android/PWA already pulls 192px and 512px from the manifest; Windows uses the ICO.

Browser and Platform Compatibility

This focused ten-file favicon setup provides complete coverage:

Google Chrome — Prefers the SVG icon, falls back to ICO
Mozilla Firefox — Full SVG favicon support
Microsoft Edge — Uses SVG icon on Chromium-based versions
Safari (macOS) — SVG favicon support since version 15
Safari (iOS) — Uses apple-touch-icon.png for home screen bookmarks
Chrome (Android) — Reads icons from manifest.webmanifest
Internet Explorer / Legacy Edge — Falls back to favicon.ico
Opera, Brave, Vivaldi — Chromium-based, uses SVG icon

Favicon Implementation Checklist

Design your icon as an SVG (favicon.svg) with optional prefers-color-scheme: dark media query
Export PNG versions: 96×96 (root favicon.png) plus 16×16, 32×32, 48×48 in /favicons/
Export a 192×192 PNG (favicon-192.png) for Android home screen
Export a 512×512 PNG (favicon-512.png) for PWA splash screens
Convert or export a 256×256 pixel .ico version for legacy browser support
Export a 180×180 PNG with 20px inner padding for Apple devices
Create a manifest.webmanifest file referencing both Android PNGs
Add the link tags to every page's head section

Common Favicon Mistakes to Avoid

Using only favicon.ico — You miss out on crisp SVG rendering and proper mobile home screen icons.
Forgetting the apple-touch-icon — iOS will show a low-quality screenshot of your page instead of your icon.
Skipping the manifest — Android Chrome won't display your icon correctly for installed PWAs.
Generating 20+ icon files — Unnecessary complexity that adds no real-world benefit over the focused ten-file approach.
Not testing dark mode — An SVG favicon that looks great on light backgrounds may be invisible in dark mode without the media query.

Free Favicon Checker

Validate your favicon setup across ico, PNG sizes, and SVG.

Free Favicon Checker: Check Icons for Every Platform

Run a focused favicon check to confirm your icon loads everywhere it should: browsers, mobile home screens, and search results.

What we validate for you:

favicon.ico availability and correctness.
Apple touch icon and Android icon readiness.
Common PNG sizes used across major platforms.
SVG support for modern browsers.
Clear pass/fail results for quick fixes.

Favicon Creator

Upload an image and generate all the favicon files you need.

📁

Click to upload or drag & drop your image

PNG, JPG, or SVG — at least 512×512 recommended

Generated Icons

HTML Code

Path: Default: favicon.png + favicon.ico in /, everything else in /favicons/

Manifest Editor

name

short_name

start_url

display

theme_color

background_color

Bing / Windows Tile (browserconfig.xml)

We generate a browserconfig.xml with Windows tile logos. It’s also included in the ZIP.

Favicon Analysis

Favicons help your site stand out in browser tabs, bookmarks, and search results.

Create Icons Get Free Consultation

Need Help Fixing These Issues?

Our team of experts can help improve your website's favicon and branding setup.

Get Free Consultation Create Icons View Our Services

Favicon Not Showing in Google? Fix It Fast