EzMsg

A workspace for researchers to prepare and preview study messages.

My role: Messaging sandbox, authentication, and role-based access
With: UTSA Mobile Lab / 2026

A research message is more than a line of text. The wording matters, but so does when it arrives and what happens after someone replies. EzMsg grew out of the need to work through those details away from a live study.

Public EzMsg introduction page with an illustrative message sequence, not the research application — Public introduction website. The message sequence is an illustrative example. No messages are sent, and this is not a capture of the research application or a live study.

What I worked on

I worked on a separate messaging workspace where researchers could prepare and preview protocols. Timing, content, and access for different researchers all had to fit together.

For the public website, I made that idea easier to explore through a small message sequence. You can choose a step and read the message in context, without needing access to the research application.

Visit the public introduction

This link is the public project introduction, with an illustrative message preview. It does not send messages or open a live study. The research application is separate and unverified.

More context and technical details

The point of a sandbox is being able to change something, inspect it, and try again. Keeping that work apart from live delivery gives preparation its own space.

The Vercel site is a public introduction with illustrative messages. It does not send messages or give access to a live study.

Next.js, Node.js, Docker, GCP, PostgreSQL, Redis

The previous research-application sign-in did not respond within 20 seconds on 2026-09-17. That does not establish a working study workspace. The public introduction is separate: no messages are sent, and there is no live study access from this site.
Last reviewed: 2026-09-17

Next: Gimmie