Containers & hierarchy

Real storage is nested — a bin on a shelf in a closet in a room. Packle's data model is built to match that, not fight it.

How the hierarchy works

Every item in Packle can also be a container — there's no separate "folder" type sitting next to the item type. A container is an item that holds other items, and it can hold anything: other containers, plain items, or a mix of both. Nest containers inside containers as many levels deep as your actual storage needs — a bin inside a shelf inside a closet inside a room is a completely normal hierarchy, and Packle doesn't force you to flatten it into tags or categories instead.

This single concept — item, optionally container-flagged — replaces what other systems split into folders, categories, and locations. You never have to decide up front which system a given box belongs to; you just nest it where it physically is.

Creating and nesting containers

Flip the "this is a container" toggle in the item editor to turn any item into one. From then on, tapping that item takes you inside it instead of to a detail view — you'll see whatever's already there, plus the "+" button to add more. Move an item into a different container at any time by editing it and changing its parent; Packle blocks moves that would create a loop (an item can't end up containing itself, however many levels up).

Breadcrumbs and navigation

Every container view shows a breadcrumb trail across the top — the chain of ancestors from the root down to where you're standing. Tap any crumb to jump straight back to that level instead of backing out one tap at a time. If you're nested unusually deep, the trail collapses to keep it readable, but it still gets you back to any ancestor in one tap.

Reordering with drag-and-drop

Items and containers can be dragged into whatever order makes sense to you within their parent container — most-used stuff up top, rarely-touched stuff at the bottom, whatever matches how you actually think about the space. The order is saved per container and persists the next time you open it; nothing resets to alphabetical or creation-date on you.

Deleting a container

Deleting something that might have things inside it is exactly the kind of action that deserves a confirmation step, so Packle shows you what's at stake before anything is removed — specifically, a count of how many items are nested inside. From there you choose how the delete resolves:

• Cascade — delete the container and everything inside it, all the way down.
• Move — relocate the container's direct children somewhere else first, then delete the now-empty container.

Both paths need that explicit choice; nothing gets deleted just because its parent did without you seeing the blast radius first.

Once you've got containers nesting the way you want, Labels & printing is the natural next stop — a label on the outside of a box is what turns "I organized this" into "I can find this without opening it."