From Eight Admin Tables to Phone Cards Without Dropping Fields
We mapped admin columns to phone fields and retained a scrollable comparison table, with explicit costs for duplicate DOM and nested record actions
Reviewed by Dmytro Nasyrov on October 22, 2026.
We ported eight administration tables during the redesign, but did not force all eight into the same phone layout. Most became record cards. Evaluation run history retained a horizontally scrollable table because comparing neighboring values still mattered there. The work covered users, companies, sources, versions, feedback, conversations, the benchmark and run history. The central requirement was to retain each record's useful fields and actions when desktop columns no longer fit, without making the page itself scroll sideways.
Map information before choosing a smaller layout
A desktop row combines identity, attributes and actions in a compact horizontal arrangement. A phone card needs explicit places for those responsibilities. We mapped the existing columns into named card content rather than selecting only the visually convenient fields.
The card used a description list for labeled attributes. Its title could open the record, while secondary actions remained separate controls. This gave a reviewer a way to check whether the mobile representation retained the same information, instead of judging it only from its appearance.
| Desktop responsibility | Phone representation |
|---|---|
| Record identity | Named title or destination |
| Attribute columns | Labeled description-list fields |
| Status | Visible status text and styling |
| Secondary operations | Independent controls with their own targets |
| Comparison-heavy run history | Locally scrolling table |
Run history was the deliberate exception. A card can make one record readable while making comparisons across records more cumbersome. The dataset's job determined whether vertical records or a retained table was the better representation.
The eight-table representation map
| Table | Phone identity and retained fields |
|---|---|
| Users | Name, status and email; access role, profession and company; actions menu |
| Companies | Name; user count and creation date; Rename |
| Sources | Title, status, byline and failure; device, type/tier, active version, pages, fragments, weight and update |
| Versions | Label, active mark, status and filename; size, pages, fragments, upload/index dates; Make active and Open PDF |
| Feedback | Answer excerpt, kind and status; reporter and date; open report |
| Conversations | Title; owner, message count and last activity; open conversation |
| Benchmark | Question, latest result and expectation; source and topic |
| Run history | Retained scrolling table with its metric columns together |
This is the recorded field map, with neutral labels rather than live records. It makes omissions reviewable per table instead of relying on one attractive card example.
CSS selected between two representations
We rendered the table and card forms and let CSS select the visible one. Phone rendering therefore did not wait for client code to discover the viewport width and replace a desktop layout after mount. That choice carried a cost: duplicate DOM representations. Tests had to distinguish visible interaction from hidden copies, and both forms had to share the same data and operation contract. Rendering two independent implementations with diverging fields would simply move the inconsistency into the component.
The duplication was bounded to presentation. We did not use separate phone data with fewer fields to make the cards easier to fit. A newly added column still needed an explicit mobile mapping or a documented reason to remain in the scrollable representation.
A row click could collide with an action
Clickable records also contained links, buttons and menus. A click on one of those controls must not additionally trigger the row's open action. Portalled menu content made a simple visual containment assumption insufficient. The shared behavior ignored interactions originating from those nested controls, including the relevant portalled cases. Tests exercised that boundary. Otherwise a phone user could attempt a secondary operation and unexpectedly navigate away from the record being acted on.
We treated the record title as a real navigation responsibility and the action controls as operations with separate semantics. Making the entire card look interactive did not remove that distinction.
The phone checks were deliberately bounded
The implementation merge reports checks at 1440 and 390 pixels in both themes, with additional Ukrainian and German phone inspection for users and sources. Its end-to-end scenarios checked card fields and page overflow.
Those observations do not mean every locale, browser and record length was independently inspected. The original merge left pagination-end focus behavior and some non-table touch targets as open work. We retain those limits rather than using the successful card port as a blanket usability claim.
The reusable artifact was the field map
Shared components supplied common mechanics, but each table still needed its own information mapping. The table above is the review shape we can reuse: identify the record, retain its attributes, separate its actions and decide whether comparison should stay horizontal.
No task-time improvement was measured. The recorded outcome is narrower: an implemented responsive representation, explicit exceptions and browser evidence for selected phone cases. Use synthetic records in layout comparisons to avoid disclosing user or company data.
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.
