A to-do app for Android. Add, edit, and long-press to remove tasks; tasks persist across sessions.

Role

Developer

Timeline
September 2021

Technologies

  • Java
  • Android SDK

Tools

  • Android Studio
  • Git
  • GitHub

Background

One of my very first apps, built through CodePath's Android course. The point was learning fundamentals like user input and persistence. Can I make data survive closing the app?

Solution

A single task list. Type a task and add it, long-press to delete, tap into a second screen to edit text. The list saves to local storage so it's still there after a restart.

Process

I built the main screen first, then list management, then persistence. Persistence got most of the attention because it was the actual learning goal. Tested by adding items, force-closing the app, and verifying state came back.

Final Product

Impact

Did its job and taught me the core loop of Android development: input, state, storage.

Reflection

First exposure to handling taps vs long-presses and passing data between screens. Reminders and categories would be the natural evolution if I picked it up again.