Packsense - Week 4
One Hour a Day is Better Than Nothing
Life got in the way this week. No long sessions, no deep focus blocks, no losing track of time while debugging something that should have taken ten minutes. Just about an hour a day carved out between everything else — enough to keep moving, not enough to do anything dramatic.
As it turns out, an hour a day for three days is still three hours of work. And three focused hours on the right things can move the needle more than a full day spent context-switching. This week was proof of that.
Day 16: Designing the Logic System
Before writing a single rule, the first day was spent thinking through the structure of the whole suggestion system. How many trip types should the app support? How do you handle users who are meticulous packers versus those who just want to throw things in a bag and go? The answer ended up being two distinct modes for every trip type: Standard for experienced travellers who want tight, optimised suggestions, and Loose for less seasoned packers who need more breathing room without being made to feel bad about it.
With the framework defined, the first two trip types got their full rule sets: Leisure and Work — covering clothing quantities, footwear, toiletries, electronics, and bag selection, all written as explicit if/then logic the app can interpret directly.
Different type of suggestions for a standard or a loose trip
Day 17: Rules for the Outdoors
Day 2 tackled the more complex trip types: Hiking, Sport / Active, and Backpacking. These required significantly more nuance than Leisure or Work. Seasonal variations, overnight vs day trip logic, activity-specific gear flags, and weight thresholds that trigger warnings when a pack is getting too heavy for the type of travel.
A few highlights from the rule sets: hiking packs now flag essential vs optional items differently depending on whether the trail is remote; sport trips cap recommended weight at 15kg in Standard mode and 18kg in Loose; backpacking suggestions actively discourage bringing laptops and flag any single optional item over 500g for removal.
Outdoor trip and alert for when the bag is getting to heavy
Day 18: Plugging the Rules into the App and Polishing the UI
With all the logic defined on paper, Day 3 was about getting it into the app and making sure it actually worked as intended. Rules were implemented, tested against real gear combinations, and adjusted where the output felt off. A few edge cases needed extra handling — trips that combine multiple types, gear items that belong to more than one category, and suggestions that were technically correct but felt tone-deaf in context.
Alongside the logic work, a round of smaller UI adjustments kept things moving: spacing, consistency fixes, and a few tweaks to how suggestions are surfaced on the trip page to make them easier to act on at a glance.
Before and after
