AstroHelm – Use your phone camera to aim a telescope or telephoto lens
Hello HN!As an amateur astronomer living in New York City, finding objects in the night sky has always been a huge challenge. I thought about using the smartphone's gyroscope and magnetometer, but the accuracy left a lot to be desired.Then I learned about plate solving: given a picture of the sky, we can determine exactly where in the sky the camera was pointing by identifying the star pattern. This was a much better fit - as long as the phone and the optics are rigidly connected, we can repeatedly photograph the sky and determine the pointing direction with very high accuracy.A lot of work was done to design an algorithm that works reliably with smartphone cameras, which have limited light sensitivity and wider field of view which includes buildings and trees. I experimented a lot with machine learning, and to my surprise, traditional CV methods actually performed better at extracting stars from the image.The result is AstroHelm, an iOS and Android app that helps figure out where your telescope or camera is pointing, and guides you to the object of your choice. Just follow an arrow on screen, and the object will land right in your eyepiece or viewfinder. Everything happens on device, and no internet connection is required.AstroHelm is free to use and comes with beginner-friendly objects selected for each night. Optional one time purchases unlock more objects and advanced features, such as interoperability with other astronomy software. I am also proud to partner with astronomy clubs and organizations to offer free licenses for outreach.I hope AstroHelm can make it a little easier to discover the wonders of the night sky, and I look forward to your feedback!
FL score
out of 100
Verdict
high confidence
Competition
No competitor data yet
Trend
No signal yet
AstroHelm is a mobile app that uses plate solving to help amateur astronomers accurately aim telescopes and telephoto lenses without internet.
The pain
The gap
Build angle
Strengths
- Clear and specific problem with a passionate niche audience
- Innovative use of plate solving adapted for smartphones
- Works offline, increasing usability in remote or urban areas
- Partnerships with astronomy clubs for outreach and credibility
Risks
- Limited market size due to niche hobbyist focus
- Monetization depends on converting free users to paid upgrades
- Competition from existing astronomy apps with partial features
- User acquisition and retention may be slow without strong marketing
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
- Problem clarity
- 85
- Solution gap
- 80
- Willingness to pay
- 65
- Buildability
- 80
The problem of aiming telescopes in urban environments is clear and real, the solution fills a gap with a novel approach, some users will pay for advanced features, and the app is technically feasible for a solo founder.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
The idea addresses a specific pain point with a clear value proposition, but the market size and monetization potential are moderate given the niche audience.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
The product fits a defined user need and leverages existing technology well, though customer acquisition and retention may be challenging due to the niche and free-to-use model.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
The solution is innovative and technically sound, with a clear user benefit, but scaling beyond hobbyists and converting free users to paid customers could be difficult.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
The founder has identified a real problem and built a working product with a clear path to user engagement, but the market is specialized and monetization depends on upselling enthusiasts.
Five lenses, one composite. How scoring works
The angle
No market research recorded for this idea yet.
Semble – Code search for agents that uses 98% fewer tokens than grep
Hey HN! We (Stephan and Thomas) recently open-sourced Semble. We kept running into the same problem while using Claude Code on large codebases: when the agent can't find something directly, it falls back to grep, reading full files or launching subagents. This uses a lot of tokens, and often still misses the relevant code. There are existing tools for this, but they were either too slow to index on demand, needed API keys, or had poor retrieval quality.Semble is our solution for this. It combines static Model2Vec embeddings (using our latest static model: potion-code-16M) with BM25, fused via RRF and reranked with code-aware signals. Everything runs on CPU since there's no transformers involved. On our benchmark of ~1250 query/document pairs across 63 repos and 19 languages, it uses 98% fewer tokens than grep+read and reaches 99% of the retrieval quality of a 137M-parameter code-trained transformer, while being ~200x faster.Main features:- Token-efficient: 98% fewer tokens than grep+read- Fast: ~250ms to index a typical repo on our benchmark, ~1.5ms per query on CPU (very large repos may take longer)- Accurate: 0.854 NDCG@10, 99% of the best transformer setup we tested- MCP server: drop-in for Claude Code, Cursor, Codex, OpenCode- Zero config: no API keys, no GPU, no external servicesInstall in Claude Code with: claude mcp add semble -s user -- uvx --from "semble[mcp]" sembleOr check our README for other installation instructions, benchmarks, and methodology:Semble: https://github.com/MinishLab/sembleBenchmarks: https://github.com/MinishLab/semble/tree/main/benchmarksModel: https://huggingface.co/minishlab/potion-code-16MLet us know if you have any feedback or questions!
AI
Postgres extension for BM25 relevance-ranked full-text search
Last summer we faced a conundrum at my company, Tiger Data, a Postgres cloud vendor whose main business is in timeseries data. We were trying to grow our business towards emerging AI-centric workloads and wanted to provide a state-of-the-art hybrid search stack in Postgres. We'd already built pgvectorscale in house with the goal of scaling semantic search beyond pgvector's main memory limitations. We just needed a scalable ranked keyword search solution too.The problem: core Postgres doesn't provide this; the leading Postgres BM25 extension, ParadeDB, is guarded behind AGPL; developing our own extension appeared daunting. We'd need a small team of sharp engineers and 6-12 months, I figured. And we'd probably still fall short of the performance of a mature system like Parade/Tantivy.Or would we? I'd be experimenting long enough with AI-boosted development at that point to realize that with the latest tools (Claude Code + Opus) and an experienced hand (I've been working in database systems internals for 25 years now), the old time estimates pretty much go out the window.I told our CTO I thought I could solo the project in one quarter. This raised some eyebrows.It did take a little more time than that (two quarters), and we got some real help from the community (amazing!) after open-sourcing the pre-release. But I'm thrilled/exhausted today to share that pg_textsearch v1.0 is freely available via open source (Postgres license), on Tiger Data cloud, and hopefully soon, a hyperscalar near you:https://github.com/timescale/pg_textsearchIn the blog post accompanying the release, I overview the architecture and present benchmark results using MS-MARCO. To my surprise, we were not only able to meet Parade/Tantivy's query performance, but exceed it substantially, measuring a 4.7x advantage on query throughput at scale:https://www.tigerdata.com/blog/pg-textsearch-bm25-fu
AI
GlycemicGPT – Open-source AI-powered diabetes management
I'm a Type 1 diabetic and software engineer. Last year I went months between endocrinologists with no clinician reviewing my data. I'm an engineer, so I built the tool I needed — and now I'm open sourcing it. GlycemicGPT is a self-hosted platform that connects continuous glucose monitors, insulin pumps, and existing Nightscout instances to an AI analysis layer running on your own infrastructure. Data sources:Dexcom G7 (cloud API) Tandem t:slim X2 and Mobi pumps (direct BLE) Nightscout (point it at your existing instance and you're running in minutes)What the AI layer does:Daily briefs summarizing overnight and 24-hour patterns Meal response analysis Conversational chat with RAG-backed clinical knowledge Predictive alerting with configurable thresholds and caregiver escalationImportant: this is monitoring and analysis only. GlycemicGPT does not deliver insulin, does not control your pump, and is not a closed-loop system. It reads your data and gives you insight on top of it. Your clinical decisions stay between you and your care team. Architecture:Self-hosted via Docker or K8S — the GlycemicGPT stack runs entirely on your hardware BYOAI — bring your own AI provider. Use Ollama for fully local operation (no data leaves your hardware), or point it at Claude, OpenAI, or any OpenAI-compatible endpoint if you prefer a hosted model. Data flows directly from your instance to the provider you choose; nothing is routed through any centralized service operated by the project. GPL-3.0, no subscriptions, no vendor lock-inStack:Backend API: FastAPI, Python 3.12, PostgreSQL 16, Redis 7 Web Dashboard: Next.js 15, React 19, Tailwind CSS, shadcn/ui AI Sidecar: TypeScript, Express, multi-provider proxy Android App: Kotlin, Jetpack Compose, BLE Wear OS: Kotlin, Wear Compose, Watch Face Push API Plugin SDK: Kotlin interfaces, capability-based, sandboxedLooking for contributors — especially folks with BLE/Android experience or anyone in the diabetes tech spa
AI
Questions about this idea?
FlyBot reads the scoring and gives you a second opinion on “AstroHelm – Use your phone camera to aim a telescope or telephoto lens”.