By continuing to use this site, you agree to our updated Privacy Policy and Terms of Use. ×



preFlect is an App that allows you to efficiently capture ambient event information about a photo being taken by a photographer, and embed this information back into their own photo as an additional "track" of information.

This allows anyone who has a copy of the photo to retrieve additional information captured about the event, including pictures of the photographer, and the physical location it was taken.

preFlect also allows you to selectively add additional comments and information to the photographers photo at a later time.


In the context of preFlect, flecting is a term that collectively refers to:

- Capturing ambient event information while someone else is taking your photo, such as pictures of the photographer, your current location, and other information

- Displaying a flect ID on your phone that links their photograph to the captured event information

- Presenting the flect ID into the photographers field of view, such that it can be clearly captured as part of their photo

In summary, flecting allows you to embed information about the photographer and their surroundings into their own photograph, such that it can be retrieved at a later time by anyone who has a copy of their photo.

Flect ID

A flect ID is a generic term for a code represented as an image that can be visually embedded within someone's photograph, and is capable of allowing cross-referencing of the photograph to additional event information.

The flect ID is displayed on your device's screen while you are flecting, and captured by the photographer when they take a photo.

preFlect currently uses the industry-accepted QR Code standard to represent a flect ID.

Photographic Event

A photographic event is a simply collection of ambient information, such as pictures of the photographer, current physical location, and other information that is captured while you are flecting a photograph. When a flect ID is captured as part of someone's photograph, it can be used by anyone else who has the photo to retrieve information about the original photographic event.

Each photographic event is published to a separate and initially empty event folder on Google Drive.

Captured Event

Captured events are a type of photographic event that are created when you press the "Start" button to start flecting someone's photograph.

Captured events appear as "Captured (Not Published)" or "Captured (Published)" under Events, and can be viewed and managed from here.

Published Event

Published events are captured events that have been made available to others using the publish feature of preFlect. Once an event is published, it becomes available to anyone who uses preFlect to analyze the photographer's original photo.

Published events appear as "Captured (Published)" under Events, and can be viewed and managed from here.

Retrieved Event

Retrieved events are captured events typically created by others, that are retrieved when preFlect analyzes a photograph that you received, and detects a valid flect ID. The flect ID is used to retrieve the published information about a photographic event.

Retrieved events appear as "Retrieved (From Photo)" under Events, and can be viewed and managed from here.

Events Folder

The events folder is a device-specific folder created on your Google Drive account that is used to store and publish information about all of your photographic events. Under this folder, a separate and initially empty event folder is created to store information about each photographic event. The events folder will be created in the root of your Google Drive, and is named as follows:

For iPad

For iPhone

[nnnnn] is a device-specific identifier to prevent folder naming clashes.

Event Folder

An event folder is a folder created on your Google Drive account under your root events folder to publish information about a specific photographic event. This folder is created ahead of time, and is initially empty, until you use it to publish photographic event information. Each event folder is named using a unique alphanumeric identifier.