Measuring Explored Chapters From Reader Citations

Reviewed by Dmytro Nasyrov on October 22, 2026.

Our Progress screen counted chapters explored through the reader's answer citations. It did not observe pages read, knowledge acquired or professional competence. Naming that boundary was as important as moving the screen from a single demonstration book to real library data.

Explored described a citation event

In the service, a viewer's answer citation range was checked for overlap with a source section. That overlap could mark the section as explored. A user might receive a citation without reading the chapter, and might read a chapter without generating a citation. The interface could not infer either missing behavior. We kept the metric's label tied to its actual signal. Calling it a completion rate or learning score would have added an educational claim that the stored events did not support.

Source shape changed the available navigation

The integrated Library handled sources with approved contents, flat files and recordings. When approved contents were unavailable, it still needed a whole-source fallback. The absence of a chapter tree did not mean that the source was absent from the Library. Previously, client helpers reconstructed citation placement. The integration read the service's citation-place field instead, using that common interpretation for Evidence, History and Continue. A frontend consumer should not quietly compute a second chapter assignment from a different page-offset assumption.

The fixture separated leaf counts from outline depth

The Library helper tests treated units as the leaves a reader can open, rather than counting every structural heading as another learning item. Their synthetic book contained two units under a part and two under a nested section. Both containers reported one explored unit out of two. A leaf counted itself and could report zero explored out of one.

expect(countUnits(P1)).toEqual({ explored: 1, total: 2 })
expect(countUnits(S3)).toEqual({ explored: 1, total: 2 })
expect(countUnits(B2)).toEqual({ explored: 0, total: 1 })

This fixture catches a quiet denominator change. If a component counts the part heading and its section heading alongside the leaves, the displayed fraction changes even though no reader event has changed. The unit definition has to stay consistent across the overview and the Progress view before either fraction is meaningful.

A separate preview fixture made selection and display order explicit. Six units had citation-related question counts of zero, two, zero, five, two and one. The preview chose units b, d and e, then displayed them in book order. The highest count did not move d to the first visual position. Ties also followed book order, and a partially populated selection filled from the earlier units. These counts personalize navigation. They do not upgrade citation events into evidence that the reader studied the selected units. Showing a frequently cited chapter earlier is a layout decision based on recorded questions, with the same observation limit as the explored flag.

One target can be an outline or the whole source

The helper tests distinguished a source with contents from a flat file. A source with an outline opened its Library overview; a source without that structure opened the whole-file representation. A part or section could resolve to its first available unit. Recordings used a recording target, including when the approved structure represented the entire recording as one unit.

That target classification belongs before page-specific rendering. Otherwise a source without contents can fall through a chapter-only component and appear missing, or a recording can inherit a PDF page action. Consuming the service's source shape and citation place gives each surface the same object to name. It still leaves the service responsible for what is visible and what counts as a citation overlap.

A disappearing section remained a visible record

When a bookmarked section left the Library, the bookmark row remained and its section target became null. We displayed No longer in the Library rather than silently hiding the item. The record still explained what had happened to the reader's collection.

Similarly, an invalid section could be refused before sending a new question. It was better to expose the stale target than submit a request under an unintended context. These are frontend representations of service decisions; they do not make the frontend owner of source visibility or progress calculation.

The migration included an explicit reset

The source integration introduced new identifiers. Old chapter links and interests were deliberately reset, while saved answers and passage bookmarks had their own preservation boundary. We do not call that a lossless migration of every reader object. A follow-up corrected the migration reference from V11 to V12. That was a documentation correction, not another feature. Keeping it in the chronology prevents a reader from treating an obsolete migration label in the earlier plan as the final implementation instruction.

Browser checks found presentation mistakes

The merge reports checking against the local development cluster with the backend and identity service. Repeated book/chapter titles and compact cards for childless parts were corrected during that work. Those observations belong to the integration record, rather than a claim that a unit suite guaranteed useful labels.

Earlier plans already discussed citation-derived progress. We use those as historical context, not proof that one developer originated every learning semantic. Stas's documented implementation contribution is the later Library and Progress integration and its frontend consistency.

Keep the measurement claim small

No retention, reading-time or educational-outcome study was recorded. The screen can help a reader navigate previously cited material while remaining unable to assess what the reader understood.

FAQ

Last updated: October 22, 2026

Quick answers to common questions about custom software development, pricing, process and technology.

Expand all Collapse all

Search FAQs

Type to filter questions and answers. Use Topic to narrow the list.

Showing all 14

• How long have you been in business?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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?

  Copy link Copies a direct link to this answer to your clipboard.

  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.