Microcopy and UI Text Framework

Microcopy & UI Text Framework for Nourish Mobile App

Brand Voice Principles

The Nourish app’s microcopy follows these core principles that balance our friendly, supportive personality with clear user guidance:

1. Encouraging without pressuring: We motivate users through positive reinforcement rather than guilt or urgency.
2. Clear over clever: When clarity and creativity conflict, clarity always wins.
3. Human, not technical: We speak like a knowledgeable friend, not a nutrition textbook.
4. Personally relevant: We acknowledge users’ unique wellness journeys.

Button Labels

Primary Action Buttons:

• Use active verbs + clear object structure
• Max 2-3 words whenever possible
• Should complete the thought “I want to…”

✅ “Add to meal plan” (not “Submit” or “Continue”)
✅ “Find recipes” (not “Search” or “Browse options”)
✅ “Track water” (not “Input hydration data”)

Form Field Guidance

Input Labels:

• Conversational but concise
• Include units where applicable
• Use sentence case consistently

Helper Text:

• Proactively answer common questions
• Provide format examples for complex inputs
• Keep under 140 characters

Examples:

Label: Daily step goal

Helper text: Most users start with 8,000-10,000 steps. You can adjust this anytime.

Label: Food allergies

Helper text: Select all that apply. Your meal recommendations will exclude these ingredients.

Error Messages

Structure:

1. Acknowledge the issue with empathy
2. Explain what went wrong in simple terms
3. Provide clear next steps to resolve

Examples:

“Hmm, we couldn’t find that food in our database. Try checking the spelling or add it as a custom item.”

“Your password needs a bit more strength. Include at least 8 characters with a mix of letters, numbers, and symbols.”

“Looks like you’re offline. Once you reconnect, we’ll sync your meal data automatically.”

Confirmation & Success States

Structure:

1. Confirm the completed action
2. Reinforce the benefit when relevant
3. Suggest a valuable next step (optional)

Examples:

“Meal plan saved! Your grocery list is now updated with everything you need for the week.”

“Workout logged! You’re making great progress toward your weekly activity goal.”

“Water tracked! You’re 75% to your hydration goal today.”

Loading States

Keep users informed and engaged during wait times:

“Finding meals that match your preferences…”

“Crunching your nutrition data from this week…”

“Syncing your latest activity…”

Empty States

Turn empty data states into opportunities:

Meal tracker (first use): “Ready to start tracking? Add your first meal to get personalized nutrition insights.”

Recipe favorites (empty): “Find recipes you love and save them here for quick access anytime.”

Activity history (no data): “Your activity journey starts with a single step. Track your first workout to see your progress here.”

Critical User Flow: Meal Planning

Initial Setup:

• CTA Button: “Create your meal plan”
• Helper text: “This takes about 3 minutes and helps us personalize your experience.”

Dietary Preferences Screen:

• Title: “How do you eat?”
• Helper text: “Select all that apply. You can always change these later.”
• Options: Present as positive choices rather than restrictions
  • “Plant-based” (not “Vegan/No animal products”)
  • “Low-carb focused” (not “Carb restricted”)

Error state if no selections made:

• “We need to know a bit about how you eat to create your perfect meal plan. Select any options that apply, or choose ‘No specific diet’ to see all recommendations.”

Success Confirmation:

• “Your personalized meal plan is ready! We’ve selected recipes that match your preference for [dietary preferences] and fit your nutrition goals.”
• Secondary CTA: “Customize your plan”