Why Our Quiz Availability Depends on Reviewed Questions
The frontend offered a check only for eligible approved chapter coverage, preserving old results when a new attempt was unavailable in the current source state
Reviewed by Dmytro Nasyrov and Victor Sineglazov on October 22, 2026.
Our introductory quiz interface could be implemented and tested while a particular environment still lacked enough approved questions to offer it. Availability depended on source data and curation, not simply on shipping a button or enabling a build flag.
Eligibility belonged to the current source state
Approved questions had to cover at least four chapters. An attempt could offer up to eight questions, one per chapter. Only the active edition's approved questions from books visible in the Library were eligible. A new edition therefore needed its own curated bank; approval of an older edition did not automatically establish readiness for its replacement. For the frontend, a source appearing in the Library did not establish readiness: a visible book could still lack the approved chapter coverage needed for an attempt.
| Condition | Reader-facing consequence |
|---|---|
| Insufficient approved chapter coverage | No available introductory attempt |
| Active eligible edition and sufficient coverage | Offer the available check |
| Old completed result, no current availability | Keep the result and hide Retake |
| Profession changes | Recheck availability after the save |
A previous result and current availability could disagree
A reader could have a DONE result while the current available count was zero. Profile retained the previous result instead of erasing history to make the display look consistent. It hid Retake when a new attempt could not actually start. This required separate state dimensions. A single has-quiz boolean cannot describe an old completion, current eligibility and an unavailable retake. The product needed to preserve all three meanings without offering an action the service would refuse.
Changing profession changed the question
After the selected profession was saved, the frontend rechecked availability. Reading before that save could describe the previous profile context and leave the welcome flow offering an outdated action. The order of account update and availability read was therefore part of the integration contract.
Merged work covered the welcome and Profile states, with local development-cluster checking recorded. Curating the required coverage in every deployment environment remained manual operational work. A successful implementation suite did not establish that staging had a complete bank for every part.
Separate reads for result, attempt and offer
The saved baseline helper tests inspected a DONE response with a result and available: 0. The offer helper returned false, while the Profile adapter returned a result state with retake: false. Both outputs came from the same response, answering whether a new check is available as well as what historical work the reader can still inspect.
const historical = baseline('DONE', {
available: 0,
result: result(),
})
expect(offersCheck(historical)).toBe(false)
expect(profileBaseline(historical)).toEqual({
kind: 'result', result: result(), retake: false,
})This is a reduced synthetic fixture, with the original helpers retained. A component that replaces every unavailable offer with an empty Profile row would lose the result despite a correct availability calculation. A component that infers Retake from DONE alone would expose a new attempt the present bank could not support.
Another fixture puts an unfinished attempt beside an older result. Profile gives the in-progress attempt priority and shows its answered and total counts. A later skip can still leave the previous result available for display. These states need an explicit precedence rule rather than a boolean derived from whether any result exists.
Ready could acknowledge answered work without inventing completion
The helper also distinguishes an IN_PROGRESS attempt whose answered count reaches its question count from one with questions remaining. If the finish request failed after every answer was saved, Ready could say that every question was answered. It did not have to label that reader as having skipped, nor could it manufacture a final DONE result that the service had not supplied.
Eligibility, a resumable attempt and a completed result can come from different moments in the source lifecycle. Switching the active edition may change the next offer without invalidating the fact that an earlier result exists. The frontend preserves those meanings while curation establishes whether a new bank is actually ready.
A rollout check should therefore include an eligible new reader, a reader with an old result and no current offer, and a reader with an unfinished attempt. The source fixtures establish the intended display rules for those states. They are not evidence that any particular deployment currently has enough approved chapters.
Readiness needed an operational artifact
An operational handoff needs a per-environment coverage table: visible book, active edition, approved chapters and the resulting availability. It should be populated from that environment's current data. A screenshot of a successful local attempt cannot replace it.
We also retained the language boundary: the interface chrome was localized, while the questions and answer options were English in this slice. Offering the flow in a translated interface did not make its educational content multilingual.
What the check means
This was an optional introduction to the learning product, not a validated assessment of professional competence or a clinical certification. Neither the number of offered questions nor a completed result establishes those broader outcomes.
Offered actions follow current availability, reread after the profession save. Question generation and storage belong to the backend contribution and curation workflow.
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.
