About

A founder-led software studio

DeviceBytes Software is small on purpose. The person who maps your workflow is the person who writes the code.

What DeviceBytes Software is

DeviceBytes Software is the software arm of DeviceBytes LLC, based in Madison, NJ. It builds custom software for service businesses, startups, and nonprofits — the kind of organisation that has outgrown spreadsheets and shared inboxes but does not need, or want, an enterprise platform.

It is deliberately a studio and not an agency. There is no account manager, no bench of subcontractors, and no team page listing people who will not be working on your project. That is a real constraint on capacity, and it is stated plainly rather than dressed up: it means fewer projects at a time, direct access to the person building the software, and nothing lost handing a brief from sales to delivery.

The wider DeviceBytes business has run device repair operations in New Jersey since 2023 — which is where a lot of the studio's opinions about tickets, statuses, customer communication, and operations dashboards come from. Those problems were encountered as an operator first.

Founder

Philip Rodriguez

Product-minded developer building complete applications from idea to production.

Philip works across the whole stack: React Native and Expo on mobile, React and TypeScript on the web, Node.js and Flask on the server, PostgreSQL and SQLite for data, and Docker, Vercel, and Google Cloud for deployment. The through-line is finishing things — taking a product from an idea to something deployed, submitted, and maintained.

Alongside the studio he manages IT operations for DeviceBytes, covering vendor relationships, security-control audits, and backup and recovery procedures. That work is the reason operations software on this site is opinionated about exceptions rather than dashboards full of totals.

He is completing a B.S. in Computer Science at Drew University, holds an Associate of Science in Information and Technology Systems from Raritan Valley, and spent the summer of 2025 on machine-learning research through the Drew Summer Science Institute — building a reproducible medical-imaging pipeline on PyTorch and Vertex AI.

Philip's personal technical portfolio covers the same projects in more engineering depth, including the ones not featured here.

Visit philipr.dev (opens in a new tab)

How we think

Four things we hold to

  • Clarity before code

    Most software problems are description problems. If the workflow cannot be written down in plain language, building it will not make it clearer — it will make the confusion permanent and expensive.

  • Maintainability is a feature

    Software that cannot be safely changed has already started dying. Tests, documentation, and boring conventional structure are what let version two cost less than version one.

  • You own everything

    Repositories, cloud accounts, domains, and developer accounts are registered to you from day one. Being difficult to leave is not something we want to compete on.

  • Honest scope

    A founder-led studio has real capacity limits. Saying so — and occasionally saying that an off-the-shelf tool would serve you better — is more useful than winning work that then runs late.

Capabilities

Selected technical competencies

Everything listed here appears in at least one project in the case studies.

Mobile

  • React Native and Expo, one codebase for iOS and Android
  • Background location, notifications, camera, and offline storage
  • In-app purchases and subscription restore
  • EAS Build, environment configuration, and store submission

Web and frontend

  • React and TypeScript application interfaces
  • Astro for fast, content-driven marketing sites
  • Accessible components meeting WCAG 2.2 AA practices
  • Responsive layouts from 320px upward

Backend and data

  • Node.js and Python (Flask) REST APIs
  • PostgreSQL, SQLite, schema design and migrations
  • JWT and session authentication with role-based access
  • Reporting, exports, and PDF generation

Cloud and delivery

  • Docker for reproducible environments
  • Vercel, DigitalOcean, and Google Cloud deployment
  • CI/CD pipelines and staged releases
  • Monitoring, alerting, and backup verification

Maps and location

  • Mapbox GL, marker clustering, and static map rendering
  • Geocoding, place search, and route matching
  • Background location capture and permission handling
  • Location privacy, including server-side coordinate randomisation

AI and research

  • PyTorch and scikit-learn model training
  • Reproducible data pipelines and evaluation reporting
  • Google Cloud Storage and Vertex AI staging
  • Model export via TorchScript and ONNX for serving

Have a software project in mind?

Let's turn it into a clear, buildable plan. A first call is a conversation about your workflow — not a sales pitch, and not a commitment.

Prefer email? Contact@DeviceBytes.com