Saving Settings One Row at a Time Still Needs a Queue
One pending save and the latest queued choice kept reader intent visible, with final-error handling and focus recovery bounded to one local control
Reviewed by Dmytro Nasyrov on October 22, 2026.
Saving each profile row independently removed a page-wide Save button, but it did not remove concurrency. A reader could choose one answer depth and then another while the first request was still pending. If both requests raced freely, an older choice could become the last persisted value.
Keep the pending choice visible
The depth control needed to distinguish the value shown to the reader, the value accepted by the service and a possible failure. Immediately resetting to the last confirmed value would make a second deliberate selection appear to vanish while saving continued.
Our local queue allowed one request in flight and kept the latest next choice. Further selections replaced that queued next value instead of opening an unbounded series of requests. When the current save completed, the queue could apply the latest remaining intent.
| Local state | Responsibility |
|---|---|
| Persisted value | Last accepted service state |
| In-flight value | Currently pending save |
| Latest next choice | Most recent intent waiting behind it |
| Visible choice | What the reader currently intends to select |
Coalescing reduced the number of meaningful transitions
The goal was to retain the last intent, not preserve every intermediate click as a separate update. A synthetic sequence A, B, C while A was pending could discard the unsent B in favor of C. Those letters describe control states, not a measured request trace. Serializing only this control's saves also kept the change bounded. We did not introduce a transactional profile system or promise coordination between devices. Another client could still update the same account under the service's own concurrency policy.
The relevant failure was the final attempted choice
The UI surfaced the last save's failure. An older failure followed by a successful newer choice should not leave the control advertising a failure for the state the reader now sees. That required the error lifecycle to follow the queued operation sequence.
This is easy to miss when tests resolve every request immediately. A useful fixture holds the first promise, changes the selection and then resolves or rejects requests in the intended order. The assertion should inspect the visible choice and final persistence request, not just the number of calls.
Holding the promises revealed what immediate mocks missed
The recorded component test created separate deferred promises for the first and second save. It selected DEEPER, selected SIMPLE before the first promise settled and expected only one request so far. The visible SIMPLE radio was already checked. Once the first promise resolved, the next call had to carry SIMPLE.
await choose('DEEPER')
await choose('SIMPLE')
expect(onSave).toHaveBeenCalledTimes(1)
expect(onSave).toHaveBeenLastCalledWith({ defaultDepth: 'DEEPER' })
// SIMPLE is already the visible pending choice.
first.resolve()
// After the queued transition:
expect(onSave).toHaveBeenLastCalledWith({ defaultDepth: 'SIMPLE' })This reduced excerpt uses choose for the test's radio-click helper; it preserves the operation order, not the complete component setup. The test distinguishes an optimistic display from a second in-flight mutation. A radio can show the latest choice without requiring every click to start an overlapping save.
Beside the pending display value, the implementation stores the next unsent value in a mutable queue. Each iteration consumes that next value, clears the slot and awaits the save. A new choice can replace the slot while the current iteration waits. The loop then consumes the latest remaining choice.
It does not replay a list of all intermediate selections.
Failure belongs to the end of that sequence
Another fixture rejects the first deferred promise with SERVICE_UNAVAILABLE, lets the second save begin and checks that no old failure alert remains. After a successful second save, it still expects no alert. A separate final-failure test establishes the other side: when the last attempted update fails, the row must say so.
After pending work ends, the displayed confirmed value comes from the parent-provided profile. The isolated fixture keeps that profile constant, so it is not evidence that a real successful SIMPLE save should revert to STANDARD. Its useful evidence is the pending choice, serialized arguments and error lifetime. Persisted-state propagation remains the parent integration's responsibility.
This distinction also explains the scope limit. Serializing this row's calls prevents this component from racing its own older intent. It cannot prevent another tab from writing the same profile, and it supplies no compare-and-swap or cross-device transaction guarantee.
Focus needed an ownership-aware fallback
The related Profile dialog could close after a profession became organization-locked. Its initiating Change button might no longer exist. The implementation returned focus to that button when available and otherwise to the relevant row. Saving and focus therefore shared a stale-state boundary: the interface that began an operation might be replaced by newer accepted account state. Retaining an obsolete DOM reference would not make the operation easier to understand.
What this implementation establishes
Serialization, latest-choice coalescing and final-error presentation are recorded in the pinned save-depth implementation. The related tests inspect that local behavior. No randomized network benchmark or user study was recorded.
Pending intent, confirmed persistence and a superseded failure can coexist. A single boolean flag cannot describe the row; the state table keeps those values separate.
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.
