Separating Connectivity From Recovery in the Chat UI
Browser connectivity only triggered a recovery attempt, while successful reads and explicit retry controlled page restoration and an interrupted question
Reviewed by Dmytro Nasyrov on October 22, 2026.
A browser could report that it was online while the application's active reads still failed. Clearing an offline screen on that browser signal alone could reveal the same broken page and imply that recovery had completed.
Connectivity errors needed a narrow identity
Our connection-loss path tagged genuine fetch failures. It did not classify every application TypeError, HTTP failure or abort as offline. An HTTP 500 is a service response, not evidence that the device lacks a connection; a canceled request is another distinct event. This kept the recovery surface tied to a failure it could address. A generic exception handler that turns every error into Check your connection would conceal application defects behind an inaccurate diagnosis.
The existing page stayed mounted
The provider retained the current page while presenting the offline state and preventing interaction with the unavailable underlying surface. That preserved local component state while the application attempted to recover its reads.
Retention did not turn the product into an offline search system. Server-backed search remained unavailable without its services. The frontend was preserving context for recovery, not claiming that it could answer from a local corpus.
| Event | Recovery meaning |
|---|---|
| Browser says online | A reason to attempt recovery |
| Active queries refetch successfully and browser is online | Permit the offline state to clear |
| Automatic reconnection | Do not automatically send the held question |
| Explicit Try again | May consume and retry the interrupted send |
A successful read was part of recovery
Offline cleared through the retry path only after active queries had refetched successfully and the browser still reported online. That combined a coarse browser observation with application evidence. Neither condition alone established the complete transition.
A refetch failure kept the recovery surface active. It did not erase the user's question or remount the page as an apparent fresh start.
Sending again required explicit intent
During connection loss, the provider held at most the latest interrupted send callback. Taking that callback consumed it. An explicit retry could use it, while an automatic online event did not send a question on the reader's behalf. This distinction matters when reconnecting without further interaction. The reader may have returned only to inspect the page, or may no longer want to issue the earlier question. Restoring connectivity should not silently become a new submission action.
The error fixture preserved a response as evidence
The network-classification tests passed an event-stream failure with no response and expected a network error. Giving that same error type a 502 Response made the classifier return false. The service had answered, even though it answered badly. A separate application TypeError also returned false, while a fetch failure tagged at the request boundary returned true.
An HTTP 500 Response passed through the fetch wrapper test unchanged. It did not throw an offline error merely because the status was unsuccessful. This keeps response handling in the service-error path and reserves the connection-loss surface for the tagged transport condition.
Recovery had a concrete read-before-reveal sequence
Before recovery, the saved helper waited for refetchQueries({ include: 'active' }). A rejection returned false and left the connection state untouched. After a successful read, it checked the browser's online flag again before restoring the page. This second observation matters because the network can change while the refetch is pending.
try {
await client.refetchQueries({ include: 'active' })
} catch {
return false
}
if (!navigator.onLine) return false
connection.restore()
return trueRepeated events kept the same store snapshot object when neither connection flag changed. Its regression called lose twice and expected the second call to preserve the snapshot, then restored the connection and checked the listener count. This bounded local state churn; it did not measure reconnection quality or the availability of every backend route.
The retry slot was consumed before another use
Another fixture held a first send callback, replaced it with a second and then took the held value twice. The first take returned the second callback; the next returned null. Holding a newer intent replaced the older one rather than building an offline submission queue.
That local invariant supports the explicit Try again flow. It still cannot tell whether an earlier request reached the server before its response disappeared. Preserving the page and consuming one callback are useful recovery behaviors with a narrower scope than exactly-once delivery.
Local consumption is not exactly-once delivery
Consuming the held callback prevents repeated local use through that path. It does not prove that a server never received the first request before its response was lost. We make no exactly-once delivery claim.
Classification, read-recovery and retry-intent behavior are supported by the pinned provider and connection tests. They do not establish a durable offline mode or a measured reduction in lost submissions.
The transition table helps keep the promise precise: the page retains context, the application verifies reads and a person decides whether an interrupted question should be sent again.
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.
