Urgent.News

What's breaking now, across thousands of outlets.

Tech

Killedar: a fort guide that works where the signal dies

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass What I Built Try it: killedar.onrender.com · Code: github.com/abhijeetkaze/killedar Halfway up Rajgad the bars on your phone go one by one. By Padmavati Machi you're carrying a very expensive torch. That's the problem with every AI trek assistant I could imagine building on a hosted API: it works in Pune and…

Killedar is an offline trek companion app designed to help trekkers navigate Maratha forts near Pune, such as Sinhagad, Rajgad, and Lohagad, when they lose signal on their journey. Created by Abhijeet Kaze, the app functions as a Progressive Web App (PWA) with three screens: Plan, Ask, and Listen.

On the Plan screen, users select a fort and trail, and enter the last bus back from the base village. Killedar then predicts the climb time based on the user's past hikes and works backward from the last bus to determine the ideal departure time from Pune. The Ask screen allows users to ask questions about the fort, such as whether there is water at a specific location or if a particular route is suitable for beginners.

The app answers these queries using Gemma, an on-device language model powered by WebLLM, which compiles models to WebGPU.

The Listen screen provides an audio narration of the fort's history, read aloud in either English or Marathi, allowing trekkers to engage with the fort's story even when their device's screen is inaccessible. To use Killedar offline, users must set it up once using their laptop or desktop computer before heading to the fort. Once set up, the app can function seamlessly with the airplane mode enabled, making it an ideal companion for trekkers who need reliable information while venturing through the Sahyadri forts.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Azure Functions vs WebJobs: Choosing the Right Tool

In cloud applications, background processing is often needed for scheduled tasks, queue processing, and operations that should run independently of an API request.

  • Azure Functions excel in event-driven workloads with various triggers.
  • Azure WebJobs operate within Azure App Service, ideal for existing App Service applications.
  • Decision hinges on scaling, reliability, idempotency, monitoring, and security needs.

How a Go `scratch` container absorbed 1,000+ probes on Day 1 with $0 infra cost

Modern web development has become bloated. A simple web application today often requires hundreds of megabytes of node_modules , complex JavaScript bundlers, heavy virtual DOM abstractions, and cloud…

  • FGOTHS framework absorbed over 1,000 probes on Day 1
  • Server-Driven UI eliminates client-side JavaScript
  • Static scratch containers incur $0 infra cost

A Small SaaS Release Checklist That Includes the Failure Path

A feature can look finished in a demonstration while still leaving the team uncertain about what happens when a request fails, a permission is missing, or a customer submits the same action twice.

  • Emphasize failure path alongside normal path in release checklist
  • Document expected outcome and failure scenarios for small software change
  • Create scenario table for valid connection, expired credentials, and more

More from Sunday 11 October →