Type: feature request
A round-up of the most-requested enhancements. Listing them together because they share a theme — making Reframe more flexible and harder to forget. Happy to split into separate issues if that is easier to track.
1. iOS version
Reframe is Android-only today. An iOS port would let iPhone and iPad users join. Most of the stack is already cross-platform Flutter; the main work is the camera and secure-storage backends (AVFoundation + Keychain) and the capture screen. The encrypted-vault and timeline logic should port over largely as-is.
2. Import from the gallery when setting up a capsule
Right now the "before" photo must be taken with the live camera. It would be great to pick an existing photo from the device gallery as the before shot — useful when you already have a starting-point photo you want to track from. This needs an image-picker flow alongside the camera on the new-capsule screen (and the same option for "after" re-shoots). On-device only, fits the privacy model.
3. Video support
Today capsules are photo-only. Potential to support short video clips as before/after frames (captured or imported), and maybe a video timeline export. This is a bigger change — it affects storage size, the encrypted vault, the gallery viewer, and export — so it is worth scoping carefully before building.
4. Notifications when a capsule is due
When a capsule lock opens and it is time to re-shoot, a local notification would nudge the user to capture. Today the app is silent: you only see "ready to capture" when you open it. Scheduled local notifications (no server required, fully on-device) would make the capture-due moment actually findable, and they fit the offline-first philosophy.
All four keep Reframe offline, private, and account-free (notifications are local, gallery import is on-device, iOS is just another platform). Discussion and pull requests welcome — please comment on which one matters most to you.
Type: feature request
A round-up of the most-requested enhancements. Listing them together because they share a theme — making Reframe more flexible and harder to forget. Happy to split into separate issues if that is easier to track.
1. iOS version
Reframe is Android-only today. An iOS port would let iPhone and iPad users join. Most of the stack is already cross-platform Flutter; the main work is the camera and secure-storage backends (AVFoundation + Keychain) and the capture screen. The encrypted-vault and timeline logic should port over largely as-is.
2. Import from the gallery when setting up a capsule
Right now the "before" photo must be taken with the live camera. It would be great to pick an existing photo from the device gallery as the before shot — useful when you already have a starting-point photo you want to track from. This needs an image-picker flow alongside the camera on the new-capsule screen (and the same option for "after" re-shoots). On-device only, fits the privacy model.
3. Video support
Today capsules are photo-only. Potential to support short video clips as before/after frames (captured or imported), and maybe a video timeline export. This is a bigger change — it affects storage size, the encrypted vault, the gallery viewer, and export — so it is worth scoping carefully before building.
4. Notifications when a capsule is due
When a capsule lock opens and it is time to re-shoot, a local notification would nudge the user to capture. Today the app is silent: you only see "ready to capture" when you open it. Scheduled local notifications (no server required, fully on-device) would make the capture-due moment actually findable, and they fit the offline-first philosophy.
All four keep Reframe offline, private, and account-free (notifications are local, gallery import is on-device, iOS is just another platform). Discussion and pull requests welcome — please comment on which one matters most to you.