LensLeap is a photography sharing and critique platform built with Next.js and Supabase. It is designed around genuine feedback and skill-based discovery rather than the engagement-optimised algorithm feeds that dominate existing platforms.
The core premise is simple: the photographers who would benefit most from honest critique get the least of it on Instagram and its alternatives. LensLeap is an attempt to fix that — a platform where the content discovery and feedback mechanics are built to serve improvement, not engagement metrics.
The challenge
Photography platforms have a fundamental tension. Instagram, 500px, and Flickr were each, at some point, genuinely useful communities for photographers. Then they were optimised for engagement. Engagement optimisation rewards novelty, emotional intensity, and broad appeal — qualities that have nothing to do with photographic craft.
The result: amateur and developing photographers get almost no useful feedback. Their work either disappears into an algorithmic void or receives a handful of "great shot!" comments that provide no actionable signal. Improvement requires honest critique. The existing platforms, by design, don't provide it.
There's also a discovery problem. When content is ranked by engagement metrics, talented photographers without an existing audience get no visibility regardless of craft quality. Follower count compounds; skill doesn't.
How we approached it
The project began with an audit of existing photography platforms — analysing their information architectures, feedback mechanisms, and discovery systems. This was followed by informal interviews with amateur photographers to understand where their current platforms failed them and what they actually needed from a community platform.
Key insights:
- Generic comment fields produce generic comments — structure the critique prompt and the quality of feedback improves significantly
- Photographers want to be found by people at a similar level, not just people who already follow them
- Real-time interaction (likes, comments appearing live) makes the platform feel alive and worth returning to
- Image quality cannot be compromised — slow-loading or compressed images immediately signal a second-rate platform
- Authentication friction is the biggest drop-off point — OAuth reduces this dramatically
What we built
LensLeap is built on Next.js with Supabase handling authentication, PostgreSQL database, real-time subscriptions, and image storage. The architecture was chosen for developer velocity and production scalability — Supabase's real-time capabilities enabled live updates for likes and comments without custom WebSocket infrastructure.
The critique system is the core product differentiator: rather than a generic comment field, reviewers are prompted with structured categories — composition, light, technical execution, emotional impact — producing feedback that is more useful to give and more actionable to receive. Discovery feeds can be filtered by skill self-assessment, photographic discipline, and equipment type.
- Structured critique system: Reviewers prompted with composition, light, technical execution, and emotional impact categories
- Skill-based discovery: Content feeds filterable by self-assessed level, discipline, and equipment — no algorithmic ranking
- Real-time interactions: Likes and comments via Supabase real-time subscriptions — no polling
- High-quality image pipeline: Upload via Supabase Storage with automatic compression and responsive format generation
- Full authentication: Email and OAuth flows with row-level security policies for user data
LensLeap was completed as a solo full-stack build over three months — from database schema design through to a production-ready application with authentication, real-time interactions, image upload, and a responsive grid gallery.
The structured critique system was validated in informal user testing as significantly more useful than freeform comment fields. Participants reported that the category prompts helped them articulate observations they would otherwise have left unspoken — and that receiving structured critique felt more credible and useful than receiving praise.
The project remains a clear demonstration of taking a product concept from problem definition through technical architecture to working implementation independently.