FAQ
Frequently Asked Questions
Answers to common questions about building apps and web platforms, testing, accessibility, and working with RedQA.
Building Apps & Web Platforms
- What kind of software do you build?
- Two things, mainly. Cross-platform mobile apps for iOS and Android using React Native, Expo and TypeScript, and full-stack web applications using Next.js, React, Node and TypeScript, usually backed by Postgres or Supabase and deployed on Vercel. We take products from an idea through to a live release, and we also join existing codebases to add features or fix architectural problems.
- Why React Native and Expo instead of native Swift and Kotlin?
- One TypeScript codebase ships to both iOS and Android, which usually costs less than maintaining two fully native apps, while still feeling native for most product use cases. Expo also covers a lot of build and release work. Where a feature needs platform-specific code, we add a native module rather than forcing a poor fit.
- Why Next.js for web applications?
- Next.js gives you server rendering, routing, API endpoints and a build pipeline in one framework. That means faster first loads, better SEO, and one codebase instead of a separate frontend and backend to keep in sync. With the App Router we fetch data on the server where it belongs and ship less JavaScript to the browser.
- How long does it take to build an app?
- A focused first release typically takes eight to twelve weeks from discovery to store submission or launch, depending on how much backend and integration work is involved. You see working software from the first couple of weeks: a build on TestFlight and Google Play internal testing for mobile, or a preview deployment for web.
- Who owns the code?
- You do, entirely. Work is committed to your repository from day one, or to a repository we transfer to you at the end. Every engagement finishes with a documented handover so your team can maintain and extend the product without us.
- Do the products you build include automated testing?
- Yes. We came from quality engineering, so we include tests for the main flows we ship, CI on the repository we work in, and accessibility considered on new UI. Exact coverage is agreed in the scope for that engagement.
General QA Questions
- What is QA testing?
- Quality assurance (QA) testing is the process of systematically evaluating software to identify defects, verify functionality, and ensure the product meets agreed requirements before it reaches users. QA covers a broad range of activities: manual exploratory testing, automated regression testing, accessibility audits, performance testing, API testing, and more.
- What is the difference between manual and automated testing?
- Manual testing is carried out by a human QA engineer who interacts with the application as a real user would. It excels at exploratory testing, catching edge cases, and evaluating usability. Automated testing uses scripts (commonly written in Playwright, Cypress, or Selenium) to run predefined test cases quickly and repeatedly. The two approaches are complementary: automation handles regression and speed, manual testing handles judgement and discovery.
- What is regression testing?
- Regression testing confirms that existing functionality still works correctly after code changes are made. When a developer ships a bug fix or a new feature, regression tests verify that nothing previously working has been broken. It is typically automated so that it can run on every deployment, and it is one of the highest-value investments in any QA programme.
- When should I use automated testing?
- Automated testing is most valuable for test cases that run frequently, change rarely, and need to be verified quickly. Ideal candidates include login flows, checkout processes, API endpoints, and core user journeys. If you are deploying code multiple times per week, automation pays for itself very quickly. For early-stage products where the UI changes constantly, manual testing is often more practical until the product stabilises.
- How quickly can an engagement start?
- For Discovery & Prototype and fixed build projects, we typically begin within three to five business days of signing. That includes a kickoff call to agree scope and architecture, access to your repository and environments, and confirmation of the communication channel (usually Slack or Teams). Larger builds may start with a short discovery phase before kickoff.
Accessibility
- What is WCAG compliance?
- WCAG (Web Content Accessibility Guidelines) is the internationally recognised standard for web accessibility, published by the W3C. It defines criteria at three conformance levels: A (minimum), AA (the legal standard in most jurisdictions), and AAA (highest). Meeting WCAG 2.2 AA means your digital product is accessible to the vast majority of users with disabilities, including those using screen readers, keyboard-only navigation, or high-contrast display modes.
- Is WCAG compliance legally required in the UK?
- In the UK, public sector bodies are legally required to meet WCAG 2.2 AA under the Public Sector Bodies Accessibility Regulations 2018. For private sector companies, the Equality Act 2010 requires reasonable adjustments for disabled users, and the incoming European Accessibility Act (EAA), which applies to UK companies selling into the EU, comes into force in June 2025. Even outside these legal requirements, inaccessible products exclude a significant portion of users and carry reputational risk.
- What does an accessibility audit include?
- A RedQA accessibility audit covers: automated scanning with axe-core and WAVE; manual keyboard navigation testing across all major user journeys; screen reader testing with NVDA and VoiceOver; colour contrast checks against WCAG 2.2 AA thresholds; and a structured report with each issue categorised by WCAG criterion, severity, and remediation guidance. For AA audits we also provide an accessibility statement draft.
Pricing
- How much does QA testing cost in the UK?
- We work on fixed projects, not monthly retainers. Discovery & Prototype starts at £3,950 (approx. $5,000). Next.js / React web projects typically start from about £9,000 (approx. $11,700). React Native iOS and Android apps typically start from about £14,000 (approx. $18,200). Test automation (Playwright, Cypress or Selenium) typically starts from about £4,950 (approx. $6,450). iOS and Android testing from about £3,950. AI and LLM testing from about £3,450. Manual / pre-launch QA from about £2,950. Accessibility audits from about £1,950. USD figures are approximate.
- Can I switch plans or scale up or down?
- Yes. If scope changes mid-project we agree a written variation before extra work starts. For follow-on projects we quote the next fixed scope separately so you stay in control of cost.
- Do you offer one-off testing engagements?
- Yes. We offer project-based engagements for product launches, major releases, or one-time audits. Contact us for a custom quote tailored to your specific needs.
- Do you sign NDAs and comply with data regulations?
- Yes. We sign NDAs as standard and can operate within your GDPR and applicable data protection requirements. Security and confidentiality are core to how we work.
- How quickly can you get started?
- For Discovery & Prototype and fixed build projects, we often start within about a week once scope is agreed and capacity is free. We confirm the start date in writing rather than promising one upfront.
Tools and Technology
- What is Playwright and why do you recommend it?
- Playwright is an open-source test automation framework developed by Microsoft. It supports Chromium, Firefox, and WebKit browsers; runs tests in parallel; auto-waits for elements to be ready before interacting with them; supports network interception and mocking; and produces traces and video on failure. For most modern web applications, Playwright is our primary recommendation because it is fast, reliable, and the test code is readable and maintainable.
- What tools and platforms do you support?
- We work with all major platforms including web, mobile (iOS and Android), desktop apps, and APIs. Our automation stack centres on Playwright, but we also support Cypress, Selenium, and Appium depending on your needs. For CI/CD, we integrate with GitHub Actions, GitLab CI, Jenkins, and CircleCI. For performance, we use k6 and Lighthouse.
- Can you integrate with our existing CI/CD pipeline?
- Yes. Integrating automated tests into your CI/CD pipeline is a core deliverable on our build and test automation projects. We configure GitHub Actions, GitLab CI, Jenkins, or your chosen pipeline tool to run the test suite on every pull request or deployment, report results directly in your workflow, and block deployments if critical tests fail.
Still have a question?
We're happy to answer any questions about your specific project, stack, or testing requirements.
Ready to protect the next release?
Tell us whether you need Playwright, Cypress or Selenium automation, iOS and Android testing, AI and LLM testing, WCAG accessibility, or a Next.js or React Native build. We'll come back with an approach, a timeline and a quote.