A Session Can End Without Taking the Reader's Question With It
Terminal sign-in recovery kept unsent text for its reader and page, while explicit sign-out and newer sessions in another tab required different handling
Reviewed by Dmytro Nasyrov on October 22, 2026.
A reader could finish typing a question just as the application discovered that its session could no longer be refreshed. Redirecting immediately to the landing page removed both the work in progress and the page that gave it context. We changed the frontend recovery path to preserve that context through sign-in.
This work began after terminal authentication failure. It did not replace backend token rotation or normal background refresh. The difficult frontend boundary was deciding what to preserve, who could receive it and whether a late failure still described the browser's current shared session.
Terminal loss kept the page visible
The new dialog appeared over the current page only when refresh could no longer recover the session. Ordinary refresh did not open it, and the sign-in page did not show it. Keeping the current page behind the dialog made the recovery destination concrete. The dialog could not be dismissed while the session was gone. Its action led to sign-in with the current path and query carried as the return destination. A failed attempt to clear the old session returned the dialog to an actionable error state rather than leaving a disabled button indefinitely.
The admin application reused the same dialog behavior with its own login route. The reader application added the separate responsibility of retaining the composer's unsent question.
A draft belonged to a reader and a page
We mirrored nonblank composer text into tab-scoped sessionStorage. The stored record included its owner identifier, and the key identified the page. Reading a draft required the current owner to match the stored owner. This prevented a shared-device recovery flow from handing the previous reader's question to a different signed-in user. Once the current identity was known, records belonging to someone else, or records without a valid owner, were dropped.
Blank or sent text removed the stored copy. Explicit Sign out forgot the draft records. Sign in again preserved them for the matching owner. Those two actions could share authentication machinery while carrying different work-preservation intent.
| Transition | Draft policy |
|---|---|
| Recover session, same reader and page | Restore that reader's unsent text |
| Another reader signs in | Discard the prior owner's draft |
| Question is sent or field becomes blank | Remove the stored copy |
| Explicit Sign out | Forget draft records |
| Storage is refused or full | Keep the live field without promising persistence |
Storage failure was a normal branch
Access to browser storage can fail, as can reading or writing an individual record. Our helper caught those failures and left the current field intact. The interface did not need a successful storage write to remain usable before navigation.
That is a best-effort promise. If storage is unavailable, leaving or reloading the page can still lose the in-memory question. We did not add durable offline storage or cross-device draft synchronization in this slice.
Binding a draft to its owner prevented accidental restoration across identities in the supported UI flow without turning sessionStorage into an authorization system. Server permissions remained the backend's responsibility.
Another tab could already have repaired the session
The session cookie belonged to the browser, while the recovery dialog belonged to one tab. If another tab signed in, calling logout from the older dialog could end the newly established session. The correct action in that situation was to reload into the current session. A late response made this harder. A request sent with the old cookie could still be in flight when another tab completed sign-in. Its refusal could arrive afterward and open the dialog. Treating response arrival order as session order would then destroy the newer session.
The implementation recorded sign-in elsewhere and bounded a grace period for a sign-in just before the local terminal failure. A recent event could explain a crossing old request; an event long before the failure did not establish that the session was now healthy. The distinction was tested explicitly.
The regression matrix included destructive intent
Focused tests covered sign-in elsewhere both before and after the local failure, a stale earlier sign-in, logout failure and exclusion of the sign-in page. Draft tests covered ownership and unavailable storage. The backend token-race problem remained a separate case.
The frontend merge reports broader package and Playwright checks, plus browser checking of the recovery dialog and retained question. Those are historical implementation receipts. They do not establish a production recovery-rate improvement.
The useful boundary is the transition table: terminal loss should preserve recoverable work, while an explicit departure or a different identity should not inherit it. The recovery button therefore needed more information than the last request's status code.
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.
