What Our UI Gallery Proved Before We Merged the Redesign
A development gallery exposed theme and component states while keeping unit evidence, browser geometry and human design comparison distinct
Reviewed by Dmytro Nasyrov on October 22, 2026.
Before merging the redesign, we kept a gallery where the shared UI could be inspected in light and dark columns together. It exposed token, font and overlay problems without requiring a reviewer to navigate every product workflow to reach each component state. The gallery was one layer of evidence. It did not prove that the administration tables or reader flows used the components correctly. We integrated those stages on a separate redesign branch while the earlier interface remained available for demonstrations.
The gallery represented reusable states
Its content followed the design kit: color swatches with source names, typography, radii, shadows, icons and component variants. Disabled, selected and error states appeared alongside open dialogs, sheets and menus. Hover and focus were exercised as live states.
Two columns kept theme differences adjacent. On phones, they stacked. The nested dark column also supplied a stronger boundary test than a full-page theme switch: component aliases and portalled overlays had to resolve inside that particular subtree.
A gallery of static default buttons would have missed those interactions. The point was to make states inspectable, including the ones that only appear after opening or focusing a control.
The route gate had to survive the build process
The development route required UI_KIT=1. Production images did not set that flag. We also needed an image built without the flag to serve the gallery when its development server later received the flag. Reading the environment at the wrong stage could freeze a not-found result into the build. The implementation therefore read the gate per request and tested that behavior against a build made without the gallery setting.
Building with the flag already enabled would not exercise the transition we needed to support. A successful response from that easier setup would leave the actual failure untested.
We kept the evidence layers separate
| Layer | Recorded responsibility |
|---|---|
| Token and helper tests | Alias values, class categories and shared configuration |
| Component tests | States, focus behavior and overlay containers |
| Standalone gallery browser checks | Rendered composition and interactive states |
| Human visual comparison | Comparison with the design source |
| Integrated application checks | Use of the components in actual product flows |
The screenshots were compared by eye. We did not run a pixel-diff system and do not describe the result as pixel-perfect parity. Human comparison and deterministic assertions covered different questions.
The recorded counts also came from different implementation states. Earlier stage replays and later merged branches had different suites. Treating their totals as one stable denominator would invent a misleading comparison.
Three integration receipts
| Recorded stage | Reported browser-suite total | Scope |
|---|---|---|
| Admin table merge | 93 successful scenarios | Table and phone-card integration |
| Ask core merge | 107 successful scenarios | Reader answer and layout stage |
| Integrated redesign merge | 117 successful scenarios | Combined design-system, admin and reader change |
These totals come from different source revisions. They are not one fixed benchmark improving from 93 to 117, and do not mean that the gallery itself contains that many independent checks.
Application integration found another class of problem
A reusable control could look correct in the gallery and still appear in an unsuitable product layout. Tables needed their own phone field maps. The Ask header needed checks for translated labels around its breakpoint. A dialog had to retain its footer when filled with a long form.
We kept those checks in their feature stages instead of adding every product combination to the gallery. That boundary made the gallery usable as a design-system surface and left application behavior with the code that owned it.
The final redesign merge reports 117 successful Playwright scenarios along with its package and build checks. The earlier component stages had their own recorded totals. These numbers identify historical receipts; they do not measure design fidelity or customer impact.
What we would carry into another redesign
The most transferable artifact is the evidence table, paired with a gallery fixture that preserves the failure-inducing layout. The dark island, runtime flag transition and actual font supplier each needed a check that the ordinary happy path would not provide. The gallery did not remove the need for keyboard review, accessibility work or product acceptance. Its contribution was to expose shared-system defects before the same component reached every screen, while keeping the limits of each check visible.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 14
No matches
Try a different keyword, change the topic or clear filters
-
How long have you been in business?
Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).
-
What services do you provide?
Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).
-
Where is Pharos Production located?
Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.
-
How big is your team?
Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.
-
What types of customers do you serve?
We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.
-
How is a custom software development company different from an agency?
A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.
Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.
-
How much does custom software development cost?
Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).
-
How long does it take to develop a custom software application?
Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.
-
What industries does Pharos Production serve?
Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.
-
Why hire a software development company instead of building in-house?
Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.
Factor In-house team Software development company Time to assemble 3-6 months (recruiting + onboarding) 1-2 weeks Upfront cost High (salaries, benefits, equipment) Lower (project-based pricing) Specialized expertise Limited to who you can hire locally Access to 90+ engineers across blockchain, AI, FinTech Scalability Slow (each new hire takes months) Fast (scale up or down per sprint) Long-term commitment Full-time employment contracts Flexible engagement models Risk High if key engineers leave Company ensures continuity and knowledge transfer For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.
-
What projects does Pharos Production not take on?
Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.
-
Why does Pharos Production use agile methodology?
We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.
This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.
-
When should you NOT hire a custom software development company?
Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.
In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.
-
What kind of projects has Pharos Production delivered?
Here are three anonymized examples from our recent delivery history:
FinTech startup - payment platform (MVP)
Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.Healthcare provider - patient portal (Full product)
Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.Crypto exchange - trading engine (Complex)
Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.
Stas Rysin is the Lead Frontend Developer at Pharos Production. His work covers the design system, reader interfaces and administration workflows of a professional learning platform for aesthetic medicine.
