HomeWorkLabContact
Production product · Web application

Get Moving Meals

Personalized meal planning shaped around real preferences, dietary constraints, and everyday routines.

Visit live product
At a glance

Built for production.

I worked across product implementation, backend logic, personalization, payments, responsive UI, and iteration after release.

RoleSoftware developer
StackASP.NET · C# · PostgreSQL
StatusLive product
Timeline2025 → present
01of 25 submissions
External recognition · August 2026

Winner, Development Challenge.

Selected for the strongest overall solution across functionality, visual appeal, efficiency, accessibility, and ease of use. The result included a $500 award and led to a professional web-development contract with GetMoving100 to continue improving and supporting the product.

Greenville Business Magazine Spartan Weekly News
Current product

One useful week.

Shaped around real tastes, schedules and routines.

See the live product
A balanced chicken, quinoa and vegetable bowl used by Get Moving Meals
Tuesday dinnerHerby chicken bowl32 min · high protein
How it works

Fewer decisions.
One useful week.

Preferences, allergies, nutrition, time and groceries move through one adjustable flow.

  1. 01Share constraints
  2. 02Get a week
  3. 03Adjust meals
  4. 04Shop and cook
Weekly planning

A complete week,
still easy to change.

A colorful selection of meals from the weekly plan
Fresh ingredients representing remembered food preferences
Preferences

Details remembered.

Grocery list

One list from every meal.

Produce
8 items
Proteins
4 items
Pantry
6 items
A prepared meal representing flexible meal planning
Flexibility

Change a meal.
Keep the plan.

Inside the product

Engineering details

Open a topic for the deeper view.

01
My roleAcross implementation and production

I contributed to the ASP.NET and C# application, PostgreSQL-backed behavior, responsive product flows, payment workflows, and iteration after release.

Backend
ASP.NET · C#
Data
PostgreSQL
Experience
Responsive UI
Production
Payments · iteration
02
The systemOne connected product flow
Web experience→ASP.NET · C#→Planning logic→PostgreSQL · payments

Only verified layers are shown. Internal topology and third-party services are not inferred.

03
PersonalizationConstraints, not random recipes

Likes, dislikes, allergies, dietary needs, goals, and medication-related food considerations shape the plan. A user can change one meal without losing a week that already works.

04
Product UXFrom feature-led to journey-led
EarlierShow the features→NowGuide the week

Clearer onboarding, fewer competing actions, and more consistent plan controls.

05
Engineering decisionsWhat stayed simple—and what became harder
Swap, don’t restart
Preserves a useful week; adds state to manage.
Plan through shopping
Connects choices to action; changes must stay synchronized.
Subscriptions are logic
Free, Basic and Pro shape access and payment outcomes.
06
Learning from productionFriction became the roadmap
What can we add?
Where does the plan stop being useful?

Next: recommendation evaluation, stronger telemetry, clearer feedback, and accessibility testing.