Skip for Now Is a Concurrency Requirement
Leaving an optional check had to survive late starts and saves, join pending completion and update Profile without making network cleanup block the exit
Reviewed by Dmytro Nasyrov on October 22, 2026.
Skip for now looked like a simple navigation action until it could be pressed while starting or saving an introductory quiz attempt. A late start response might create an attempt after the reader had left, and a late answer response might try to put the finished screen back into an active state.
Leaving was a local terminal intent
The frontend kept Skip available during loading and saving. It moved the reader onward even if finishing the server attempt failed. An optional check could not make successful network cleanup a prerequisite for leaving. That decision required two distinct ideas: the current UI run was over, and the server attempt still might need finishing. Suppressing later UI updates did not cancel an already committed request. It simply stopped that response from overriding the reader's explicit exit.
| Race | Required behavior |
|---|---|
| Skip while start is pending | Leave; finish the attempt if start returns afterward |
| Skip while answer is saving | Ignore late active-run UI state |
| Finish already in progress | Join that finish instead of duplicating it |
| Finish cannot reach the service | Still leave; the attempt may remain resumable |
A lost response did not justify another start
The flow read or resumed the available attempt before creating a new one after a missing response. Otherwise the client could confuse not receiving an acknowledgement with the server not having committed the start.
Completion used the same caution: joining an existing finish kept the local lifecycle from spawning parallel terminal operations just because different callbacks reached the same intention.
A late start still needed cleanup
If Skip happened before start returned, the callback recognized that the local run was already over and finished the returned attempt. It did not reopen the question screen. This case is easy to miss in a test that waits for every loading step before exposing Skip.
In the race tests, promises remained pending across the exit action. The meaningful assertion was which state remained visible after the late response, along with which cleanup operation was joined or invoked.
Following a start that lands after Skip
Before starting a new attempt, the hook reads the current check and can resume an unfinished one. Its late-start branch checks the local terminal flag after the start mutation returns. If the reader has already skipped, it asks the service to finish that returned attempt and returns without setting the active attempt state.
The following sequence reconstructs that branch from the saved hook. It is a control-flow explanation, not a production timing trace:
read current check -> no resumable attempt
start request remains pending
reader chooses Skip -> local run ends
start response returns an attempt
-> best-effort finish for that attempt
-> do not set the active attempt or reopen questionsOnce the UI run has finished, it deliberately does not await that cleanup call. Its failure is swallowed on that path. This leaves a real remote-state limitation: the server may still hold a resumable attempt. The user has left the optional activity, while remote cleanup remains best effort. Calling both facts cancellation would hide the distinction.
Once finishing begins, another exit joins it
A ref holds the current finish promise. The normal completion path and Skip reuse that promise rather than each initiating their own terminal mutation. When finishing fails, the hook reads the current check again before deciding what to hand to Ready. That read can reveal a committed result or an attempt whose answers all arrived even though the finish acknowledgement did not.
Before updating the visible attempt or handling a returned invalid-state error, the answer path also checks whether the local run is already over. That guard prevents a late successful answer from moving the reader back from Ready. It does not undo an answer that was already committed remotely.
Before invoking the caller's completion callback, terminal handling evicts the old myBaseline cache field. If a response is available, it then writes that response under the relevant profession. The ordering matters: a destination component can read the cache immediately on mount, before a network refresh completes. Invalidation and accepted data publication are part of the exit contract, not merely background cleanup after navigation.
Profile and Ready needed the same terminal data
Profile could otherwise keep showing an older state while a later refetch was pending. Evicting the cached read and publishing the accepted result served complementary purposes: invalidation alone could leave a stale display until the next successful read, while writing one result without invalidating the old query could leave another consumer reading a superseded object.
Partial work remained partial work
A skipped attempt was not automatically zero answered questions or a failed competence assessment. The UI needed to retain the service's actual attempt state. If the service could not be reached during exit, the attempt might remain resumable from Profile.
Cancellation of committed network work is beyond the frontend's guarantee. The recorded hook and tests establish local terminal-state handling and the associated cleanup paths. They do not establish exactly-once processing across every service failure.
The person can leave now; late operations must respect that decision without pretending that the remote state disappeared.
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.
