Selected work

The Asset voting platform and app

The product I originated, then led a team of four to build: the voting engine, apps and event technology behind a financial publisher whose rankings are the business.

Role
Lead full-stack developer, then leading a team of four
Year
2022 to 2025
Status
Live
Stack
LaravelLivewireMySQLAWSSwiftUIJetpack ComposeFirebaseFigma
The Asset app landing page on theasset.com

How it fits together

Web app

Laravel + Livewire

iOS app

SwiftUI, App Store

Android app

Jetpack Compose, Play Store

One Laravel backend

All business logic: vote eligibility, tiering, weekly caps, points, content feed, events

MySQL

Schemas and indexes designed for burst reads during the voting window, not average traffic

Buy side and sell side vote

inside the app

Asset Benchmark Research

rankings from the vote data

Triple A awards

adjudicated on those rankings

One Laravel backend serves the web app and both native apps, so a rule change ships once. The schema is tuned for the voting window, and votes flow into the benchmark data that adjudicates the awards.

On the stores

The Asset on the App Store, showing the listing, rating and preview screens
App Store listing
The Asset on Google Play
Google Play listing

The problem

The Asset covers Asian capital markets, and its business runs on reputation. Its Triple A awards have been running for over two decades and are adjudicated by a board of editors using data from Asset Benchmark Research, which rates both sides of the market: buyside investors and fund managers, and sellside custodians, banks and service providers. Those ratings decide the winners, the winners fill the awards receptions, and the receptions and rankings sell the magazine. So the survey is not a feature, it is the engine the rest of the company runs on. When I arrived it ran on forms emailed out and nominations collected by hand, once a year, for an audience of senior bankers and executives who will not tolerate a result they can dispute.

What was built

  • The voting platform that replaced the paper process. Buy side and sell side rate each other inside the app, and the results feed the benchmark data behind the Triple A programmes, from the Asian Local Currency Bond survey that has run since 2000 to G3 bonds, FX, Islamic finance and sustainable capital markets.
  • The vote integrity model, which I designed: participant tiering, weekly caps on how much any one person can vote, and a points system, so the outcome reflects standing in the market rather than whoever clicked most.
  • Native iOS and Android apps in SwiftUI and Jetpack Compose. I originated the product, designed the UI and UX in Figma, wrote the first version alone, and then led a team of four as it grew. Past 5,000 users by September 2024, almost all of them institutional rather than consumer.
  • The publisher's whole catalogue inside the app: the magazine digitised, podcasts and video with a proper player, search and filtering over the archive, and a feed ranked against each reader's stated professional interests.
  • Event technology that runs while the event is in the room: registration, QR check-in, live polling, Q&A, and in-room games including bingo for the awards receptions.
  • The operational spine behind it: a newsletter system sending daily to 100,000+ subscribers, customer service and feedback reporting for staff, sponsor and advertising placement managed through the Laravel site, Firebase and Google Analytics instrumentation, and RPA that removed recurring editorial and back-office work.

Decisions worth explaining

  • Awards integrity belongs in the schema, not the interface. Who may vote in which category, how much their vote weighs, and how a ballot is recorded and audited were settled in the data model, because the rankings are the product and a disputed result costs more than a missed feature.
  • The schema and queries were tuned for the voting window rather than average traffic. A survey that closes on a Friday means most of the year is quiet and one afternoon is not, so the read patterns that mattered were the ones under burst.
  • One Laravel backend holds the business logic and serves the web app and both native apps, so a change to how a vote counts ships once instead of three times and cannot drift between clients.
  • I sat with editorial, research, events and sales rather than taking a spec. Most of what shipped came out of those conversations turned into milestones, which is why the app covers awards, content, events and commercial in one product instead of four.

Outcome

Three years in production. The apps launched in 2023 and passed 5,000 users by September 2024, and the platform has run every survey and awards cycle since. An annual, manual, disputable process became software that runs continuously, and I went from writing it alone to leading the team that maintains it.

More work