> ## Documentation Index
> Fetch the complete documentation index at: https://committ.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# January 17th, 2026

> UI Polish: Removing Visual Clutter & Active States

# January 17th, 2026

## UI Polish: Refining the Visual Experience

Today was technically a "polish" day, but in mobile development, polish *is* the product. We focused on two specific user experience hurdles: visual clutter in lists and communicating state in the navigation bar.

***

## 🔍 The Q\&A: Scrollbars & Active Tabs

### Q: "I noticed the commit list has a visible scroll bar on the right. How can we make the content scrollable but keep the UI clean by removing that visual indicator?"

**The Answer:**

The visible scroll bar is a default behavior in React Native's `FlatList` and `ScrollView`, but for a premium "app-like" feel, we often want to hide it to avoid visual noise, especially on a clean list interface.

The fix is simple but effective. We use the `showsVerticalScrollIndicator` prop.

**In `apps/native/app/(main)/commits.tsx`:**

```tsx theme={null}
<FlatList
  data={commits}
  // ... existing props
  showsVerticalScrollIndicator={false} // The magic line
  renderItem={renderCommit}
/>
```

**Why this matters:**
It reduces visual cognitive load. The user already knows a list scrolls by the way it's presented (items cut off at the bottom); they don't need a gray bar distracting them from the actual content. This is particularly important in "immersive" apps where you want the user to focus entirely on the data (the commits) rather than the mechanism of viewing it.

***

### Q: "Moving to the navigation, the bottom tab bar needs to feel more responsive. Specifically, when a page is chosen, the logo has to be filled with the blue color #4FA0FF to denote the active state. Right now it just stays as an outline. How do we handle this state change?"

**The Answer:**

This isn't just a color change—it's an asset swap. To make a tab feel "selected," we need to transition from a lightweight "outline" icon to a heavy "filled" icon. This is a subtle but powerful cue that tells the user, "You are *here*."

**Step 1: Define the Variants**
In `BottomBar.tsx`, we expanded our data structure to hold both the inactive (outline) and active (filled) icon names.

```tsx theme={null}
// The Tabs Configuration
{
  name: 'commits',
  icon: 'shield-outline', // Inactive state: Lightweight, doesn't demand attention
  iconFilled: 'shield',   // Active state: Solid, anchors the user's location
  label: 'Commits',
  href: '/commits',
},
```

**Step 2: The Logic Switch**
Inside the rendering loop, we check the `isFocused` boolean, which React Navigation provides to tell us if the current route matches the tab. This boolean drives both the color and the icon choice.

```tsx theme={null}
// Inside BottomBar.tsx
const isFocused = state.index === index;

return (
  <TouchableOpacity>
    <Ionicons
      // 1. Swap the Icon: If focused, use the filled variant
      name={isFocused ? tab.iconFilled : tab.icon}
      
      // 2. Swap the Color: If focused, use our brand blue
      color={isFocused ? '#4FA0FF' : '#94A3B8'} 
      size={24}
    />
    <Text style={{ color: isFocused ? '#4FA0FF' : '#94A3B8' }}>
      {tab.label}
    </Text>
  </TouchableOpacity>
);
```

### Cross Question: "So we aren't just changing the color, we are actually swapping the icon asset itself?"

**Answer:**
Exactly. simply changing the color of an outline icon doesn't give enough visual "weight" to the active state.

* **Inactive:** `shield-outline` in Gray (#94A3B8) -> Low visual priority. It sits in the background.
* **Active:** `shield` (Filled) in Blue (#4FA0FF) -> High visual priority. It pops out.

By swapping `shield-outline` with `shield` **AND** applying the `#4FA0FF` color, we create a much stronger "selected" state. This creates a "Solid vs. Hollow" visual hierarchy:

* **Hollow (Outline):** "You can go here."
* **Solid (Filled):** "You are currently here."

This pattern is deeply ingrained in mobile user habits (see Instagram, Twitter/X, or Spotify) and makes navigation feel intuitive and responsive.

***

## 🏆 Summary for Day 17

We moved from functional to "feeling right."

* **Cleanliness:** We stripped away the utility-looking scrollbar to let the content breathe. This removes the "website wrapped in an app" feel.
* **Feedback:** We implemented a "Solid vs. Hollow" icon strategy for navigation, giving users immediate, clear, and high-contrast feedback on where they are in the application.

It's these small details—the absence of a scrollbar, the fill of an icon—that separate a prototype from a polished product.