Evolving Citations From Pages to Figures and Timed Media
Figures and recordings changed citation fields, history parsers and page-based progress, with code checks recorded separately from browser verification
Technically reviewed by Dmytro Nasyrov on .
Our citation contract began with a document and a page range. Adding figures and recordings exposed an assumption running through the product: every source reference had a page. A recording does not. Giving it a fabricated page would have concealed the mismatch instead of making the reference usable.
The October integration work extended citations across the backend, chat and administration tools of our aesthetic-medicine learning platform. The visible source card was only one consumer. Saved answers, handwritten clients and mocks also had to preserve the new fields, or a reference could work when first received and lose its meaning after reload.
A kind selected the address shape

The backend contract used three citation kinds: TEXT, FIGURE and TRANSCRIPT. Page fields became nullable because a transcript pointed into a recording. Figure citations still had a page, but added a figure label and an image URL. Transcript citations carried a time interval in milliseconds and a media URL.
| Kind | Source address | Product behavior required by the design |
|---|---|---|
| TEXT | Document version and page range | Keep the existing page reference |
| FIGURE | Document page, figure label and figure URL | Offer both the page and the extracted figure |
| TRANSCRIPT | Recording URL and start/end time | Show a time interval and open the recording at its start |
The contract also included modelWritten. For a figure, it distinguished a model-written description from the source image. For a transcript, the interface wording pointed readers back to the recording as the source. Adding a richer address did not make generated descriptions or transcriptions authoritative.
Every reader of the citation needed the fields
Updating a generated client alone would have missed several paths. The product used a handwritten history parser that discarded unknown fields. Other request documents selected citation fields explicitly. The mock-data shaping code copied fields one by one. Each could silently retain the old page-only representation.
The integration plan updated the shared citation fragment as well as those handwritten clients and mock shapes. That work was less visible than an image thumbnail, but it established whether the reference could travel intact from a completed answer to history and saved content.
We kept citations in the terminal answer event. The extension changed what a completed citation contained, rather than introducing partial source objects during token streaming. A client handling the final event then had the same address fields that the history path needed after reload.
Nullable pages reached beyond rendering
A page field was also used for library progress and saved-answer organization. Once transcripts could carry null pages, those calculations needed a defined behavior. The design skipped page-based progress and section links when no page existed. A figure could still count toward the section containing its source page.
Without that distinction, a recording might render correctly in chat while breaking a later progress calculation. The migration boundary was every consumer of the field, not only the component displaying the citation.
Unknown future kinds received another explicit rule. At the data boundary, they fell back to the existing text representation instead of crashing history parsing. The fallback preserved readable reference information where available. It did not claim support for an unknown media type.
An address could remain useful when media failed
For figures, the design added a thumbnail and a separate action to open the figure while retaining access to the PDF page. For transcripts, it displayed the time interval and provided a recording link with a start-time fragment. The embedded player was configured with preload="none" so a conversation containing several answers did not immediately download their recordings.
Failure behavior was part of the same contract. An unavailable image or recording left the reference card visible with a quiet availability note. Losing the ability to load media should not also erase the title, excerpt or address that explained the answer's source.
This requirement depended on the authenticated media path as well as the card. The integration record noted that the previous file route dropped byte-range behavior. Extending the citation therefore exposed transport work that a screenshot of a player could not verify. The detailed proxy implementation belongs to a separate engineering account.
What the recorded completion established
The October 9 status update says the integration was implemented and merged. It records 79 of 79 verification checks passing and a developer-reported staging deployment. It also explicitly says browser verification had not yet been performed. Those statements support a bounded implementation account, not a claim that every media interaction had been observed in a real browser.
For this article, the distinctive lesson is the address migration. A new citation kind crossed selection sets, parsers, saved history and page-based calculations before reaching the visible card. A working first render could not establish that all those paths preserved it.
Our versioned-source design explains why a saved answer keeps its original reference. This extension added another obligation: that preserved reference must retain the right kind of location. For a recording, that location is an interval in the original media.
Evidence scope: the October 7 product citation-integration specification and its October 9 completion update. Historical implementation checks and deployment statements are identified as recorded evidence; no fresh end-to-end media test or clinical validation is implied.
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.
Dmytro Ihnatov is the Lead Backend Developer at Pharos Production. He documents backend architecture and research experiments from the team's work on a professional learning platform for aesthetic medicine.