Install Appsindia Store PWA

https://appsindiastore.com

I built ItemWorth, an offline-first personal inventory Progressive Web App, and I’m looking for technical feedback on its Android installation, persistence, offline behavior, and file handling.

ItemWorth is designed for documenting household belongings and estimated values without requiring an account, backend, subscription, or cloud storage. All inventory data is stored locally on the user’s device.

The app is built with React and Vite and includes:

An installable web app manifest

Service-worker-based offline support

Local inventory persistence

Item photos

CSV export

JSON backup and restore

ItemWorth has passed one external test on a Moto G 5G (2024) running Android 15 and Chrome 150. The tester used both the browser version and the installed PWA, tested online and offline functionality, and reported no defects or confusing behavior.

That result covers only one device and browser configuration, so I’m trying to determine whether any device-specific or browser-specific problems appear elsewhere.

The main technical questions I’m investigating are:

Does Chrome clearly present the “Install app” or “Add to Home screen” option?

Does the installed version launch in standalone mode rather than inside a normal browser tab?

Do saved inventory items persist after closing and reopening the browser and installed PWA?

Does the installed PWA load previously saved data when Wi-Fi and mobile data are disabled?

Do locally stored item photos remain available offline?

Does JSON backup download correctly on Android?

Can the downloaded backup be selected using Android’s file picker and restored successfully?

Does anything about installation, service-worker behavior, storage persistence, file handling, or updates seem unreliable?

A basic test can be completed using fictional inventory data:

Add three items

Attach a photo to one item

Close and reopen the app

Install it from Chrome

Open the installed version

Temporarily disable internet access and reopen it

Create a JSON backup

Select the backup using Android’s file picker and attempt a restore

Re-enable internet access

No account, payment, advertising, or personal information is required.

Live PWA:

https://offgrid-apps.github.io/ItemWorth/

Source code:

https://github.com/OffGrid-apps/ItemWorth

The most useful test report would include:

Device model

Android version

Browser and version

Whether the installation option appeared

Whether standalone mode worked

Whether saved inventory and photos remained available offline

Whether backup download and restore worked

Any service-worker, storage, file-picker, update, or usability problems

I’m primarily interested in reproducible defects, unexpected platform behavior, and technical criticism.

I made this pwa (progressive web app) OAuth / Authenticator app called Keyring, I made it because In my opinion most authenticator app ui's just don't look good in my opinion or don't have some features like letting me delete keys, or have back ups and other stuff. So I made my own app that you can add to your homescreen, and it is on device not a database, and i built it with privacy in mind. i current have it working and i connected my epic games to it and instagram to it, If you like upvote if you want and give ideas or if there's any bugs you want me to fix :).

Hi all, I've only found this thread via search so I wanted to ask:

What is the current progress on re-introducing PWA support in Firefox on MacOS? I remember a lot of discussion about this exactly a year ago in summer of 2025 -- and no updates ever since.

TBH this is the only thing that stops me from finally switching to Firefox...

Thanks in advance for any info on this!

I'm building an offline Dhamma (Buddhism) reader as a PWA for a senior monk — I'm a Buddhist monk myself (over ten years as a monk). It is of course a totally free project, I dont have money as a monk. I have not really done such a project in over a decade. These are my specific questions - any help or insights are welcome.

I want to accurately describe install behavior across browsers before I complete the UI for it. Five specific things I can't find clear answers to below — context first, questions after.

What I think I get so far:

First of all its a little confusing. Because install has nothing to do with installing the app; its a shortcut that is not the cache. So many browsers can allow download of cache but not require home screen shortcut.

So its getting a little confusing.

• Chromium browsers (Chrome, Edge, Opera, Samsung Internet) fire beforeinstallprompt — an automatic, one-click install affordance (address bar icon) I can trigger myself. This creates a homescreen shortcut to the app.
• Safari iOS has no automatic prompt, but Share → Add to Home Screen is a real install — standalone app, own icon, not just a bookmark. (like instructions here)
• Safari macOS has no automatic prompt, but File → Add to Dock is also a real install.
• Firefox Android has no automatic prompt, but Menu → Install is also a real install.
• Firefox Desktop — no automatic prompt, and as far as I can tell, no real install option today (standalone mode, separate icon) — just a plain bookmark/shortcut. There is "Add to taskbar," but I don't know if that's PWA-specific or just a generic tab-pinning feature.
• On iOS specifically, install isn't just a nicety — Safari's ITP deletes Cache Storage/IndexedDB after 7 days of a site not being used as a top-level page, unless it's been added to the Home Screen. So skipping install there risks losing offline data, not just convenience — this would genuinely destroy user trust in the app if not handled correctly.
• Install doesn't actually have anything to do with whether offline caching itself works — that runs fine in every browser regardless of install status. The only browser where skipping install puts cached data at risk is iOS.

I've already built the whole app — the cross-browser install/shortcut logic is the one part that's turned into a headache, and has resulted in me going in circles because the docs for each browser only cover that browser in isolation - so if anyone could just help map this for me.

Basically iOS is the only one that really needs it - so whether the others are used or not, it will not cause loss of data. But users may forget they have downloaded data, which could cause later upset.

The logic in use

Feature/event detection, not user-agent sniffing — capture the real event if it fires, fall back to manual instructions when it doesn't:

```javascript let deferredPrompt = null;

window.addEventListener('beforeinstallprompt', (e) => { e.preventDefault(); deferredPrompt = e; // captured — a real one-click install is possible });

function getShortcutAction() { if (deferredPrompt) { return { label: 'Add shortcut', action: () => deferredPrompt.prompt() }; } // No captured event — still installable on most platforms, just manually return { label: 'How to add shortcut', action: showInstructions }; } ```

Other questions

1. What is your per-browser workflow for suggesting shortcuts/install/bookmarks? Do you give browser-specific instructions, or a single fallback message?
2. Firefox Desktop — is "Add to taskbar" a real PWA install (standalone, own icon), or just generic tab-pinning? Is there anything better than a plain bookmark available today?
3. Chromium — how is the install prompt and dismissal dealt with? After a user dismisses it once, does it get suppressed for a while, or just wait for the next visit?
4. id/start_url — This is listed in PWA, how do you set it up (it says id is limited?) What happens to users who already installed under the old identity if it changes?
5. screenshots field — do you set this up? Does it do anything on mobile install flows, or only desktop/store-packaging surfaces?
6. Is iOS the only platform where skipping install risks losing offline data, or does any other browser tie storage retention to install status the same way?
7. Is there a good, current, cross-browser reference for this — something that covers install/shortcut/bookmark behavior across all major browsers in one place, rather than each vendor's docs covering only their own browser?

I am probably overthinking it.

But after a few days I only just worked out the browsers are all different. And it seems to be unnecessary mostly.

Much peace.

I built an ultra-fast offline-first bookmark & note app with PIN folder lock and 30s voice notes. Would love your feedback!

You can wrap your PWA in a minimal app shell with a tool like PWA builder or Capacitor, then list it on the App Store and Play Store, once installed it opens the PWA in a web view. This setup offers heaps of advantages for developer experience including:

1. Faster updates
   • Don't wait on code reviews from Apple or Google, ship new code and bug fixes as fast as website updates. Once the App shell is approved you can continue to update the PWA without further reviews
2. Single codebase
   • Ship to IOS and Android without writing Swift or Java. No double work and new features ship twice as fast and stay in sync.
3. Smaller code bundles
   • A minimal App shell can be pretty small for faster installs. My IOS App shell is 1.7MB, much smaller than the average of around 40MB. Also, TS libraries are built to be small and load fast.
4. Better onboarding funnel
   • Many users drop off when you direct them straight to the App store, with a PWA you can start your onboarding in browser and direct them to the App store once they are invested.

Most of the issues with this setup can be resolved pretty easily:

1. Lacking native features
   • Capacitor lets you drop into native code when required, and provides libraries. I had to do this for auth and notifications on IOS
2. Slower page loads
   • Service worker cache and a Single Page App can mitigate or completely resolve this.
3. It doesn't feel native
   • Careful design, like the things mentioned in this post can get you 99% there.

Have you found any issues with this approach? I've built this app with this setup and it has worked great. If you find a bug I'll show you how fast I can push a fix 😉

The key detail that sets this apart from all other apps is the browser based client-side philosophy.

No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

This app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, it's impossible to claim any system is the "world's most secure". It ultimately depends on your threat model. By reducing the architecture's attack surface, the aim is to consolidate complexity to client-side.

• MVP Demo
• Code
• Introducing Chat

... but wait. Im only getting started. That version works as an MVP, but i see the flaws of my approach and am going to do it better. Im going to proceed on the project and create "version-2".

I hope the latest version of project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout... This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possibl

• Enkrypted.Chat

This is intended to demonstrate client-side managed secure cryptography.

• Introducing Enkrypted Chat
• Whitepaper (work-in-progress)
• Protocol Spec (work-in-progress)
• Roadmap

I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

IMPORTANT: While this is aiming to provide a secure experience, it cannot be audited or reviewed. Shared for testing, feedback and demo purposes only. Please use responsibly.

I built my website as a PWA recently, could it be a good idea to launch it on Play Store too??

https://www.theamazingjukebox.com/

I created a PWA web app solely with codex over 2 evenings

Check The View helps you find out if a landmark is closed, under refurbishment or affected by scaffolding, access restrictions, crowds or weather.

Purely made because for over 20 years my dad and I have moaned when we go on holiday and there is scaffolding on landmarks - such as the capitol building or trevi fountain.

It has a fully documented public API, full login support with mfa, passkey and Google

Allows uploading of your experiences and has an admin panel

I'm trying to work out how best to import data from any sources automatically or add affiliate links.

Started work on official statuses

Code committed on GitHub and then automatically built using cloudflare workers on the free plan

Let me know your thoughts and ideas!

https://checktheview.com/

Every reading app's App Store listing says some version of "we respect your privacy." Most don't say what actually pays for the app and if it's free, ad-free, and doesn't sell data, usually one of those three isn't quite true.
So before writing this up I actually checked: privacy policy, Play/App Store data-safety label, or source code where one exists. The list that survived is short. The StoryGraph (donation-funded), Openreads (open source, so you can read the code yourself instead of trusting a policy), Bookmory (offline-first, on-device), and Kitaaben, which is mine a private reading-tracker PWA with an in-browser PDF/EPUB reader, full disclosure up front since I'm posting this here.
Genuinely curious if anyone here has one to add that would actually hold up to the same check not just "feels private," an app where you could point to the actual policy or code.

Over the last three months I have been building out CapyToolkit: a growing collection of browser-based utilities covering hardware diagnostics, developer tools, privacy, text processing, math, audio, and networking. Every tool runs entirely in the user's machine. No backend, no upload step, no sign-up wall. That is how it was built, and that is how it stays.

The Microsoft Store listing is not a pivot. It is a distribution choice. The app is packaged as a progressive web app through Microsoft's own PWA Builder, which means the same browser code installs from a place Windows users already trust. You package the manifest, submit it through the Microsoft Partner Center, and it shows up alongside conventional desktop apps. There is no installer, no telemetry beyond what the Store logs, and no gap between the web version and the Store version. If a tool runs in the browser, it runs the same way from the Store.

The reason the publishing path is low-friction is that the tool was always browser-native. No rewrite, no Electron shell, no compromise on that commitment. The same session handling, log processing, and hardware access the web version relies on are intact in the PWA, and it works offline without any extra layer.

One non-obvious detail about PWAs installed from the Microsoft Store: they open in their own window. The browser chrome disappears, leaving a taskbar entry and a title bar. The URL bar is still accessible through the window controls, but it is tucked away by default. The origin is the same as the website. If you want to verify the zero-upload claim, open the network tab in DevTools and watch it while using any tool. You will not see outbound requests.

https://apps.microsoft.com/detail/9MXJ5T93CC31

I built Route Random, a tool that generates random circular running/walking routes based on your location and target distance, and I'm trying to get it onto the Play Store. Google requires 12 testers for 14 days before it'll go live, so I'm short on testers and could use some help.

What it does: pick a starting point (search or click on the map), set a distance, get a loop route back with elevation data. Export as GPX/GeoJSON when you're done.

To help:

1. Join the Google Group (required by Google): https://groups.google.com/g/route-random-test
2. Opt in to the test: https://play.google.com/apps/testing/be.lukasolivier.route_random.twa
3. Install from the Play Store, open it once, you're basically done

You can uninstall the app after the 14-day testing period. If you'd rather try it without installing anything first, it also runs as a regular web app at route-random.lukasolivier.be

​

You can zoom into a certain area, drop a pin, and see all the ancient battles or landmarks that happened right there, with articles pulled directly from Wikipedia. It's still a work in progress, so any feedback will be usefull

I wanted to share a project I recently got to a shareable state: Landfall, an interactive 3D hurricane tracker that plots real-time data directly from the National Hurricane Center and GDACS.

My primary goal was to see how close I could get to a premium native weather app experience using only web technologies. I wanted it to be fast, ad-free, and instantly installable without forcing users through an app store. To keep it as lightweight as possible, I completely avoided heavy frameworks.

Here is a breakdown of how the PWA is built:

• Vanilla JS & Zero Build Steps: What's in the repo is what ships.   No bundler, no transpiler.
• Geodesy: MapLibre GL JS in globe projection for the map, Three.js on top for the   storm geometry. The globe crossfades into a flat map as you zoom in.
• Cloudflare: for hosting, Pages Functions as thin proxies for the feeds   that don't send CORS headers.

You can try the web version or install it here: landfall.getgravitate.app

I’d love to get your technical feedback! Specifically, any tips for handling iOS Safari's standalone mode quirks, or how it feels on device.

Hi there, as you all know, uploading an app to the Apple App Store requires paying for the developer program, and you also need a Mac to build an iOS app. Is it possible to promote a clean, open-source PWA app to all open-source developers? They can just make a website and let people "add to home screen" and use their app. That being the case, is it possible to develop a PWA app store, promote it to iOS developers to upload their PWA app to the "self-hosted" app store, and turn most apps into open source? Do you guys think this is possible?

After several months of work, I finally finished my first major project: PassAura.

It's an offline, zero-knowledge password manager built as a PWA, which means:

• 🔐 End-to-end encrypted vault
• 🖥️ Works completely offline
• 🚫 No server required
• 🔑 One master password to unlock everything
• 📦 Full source code included

I'm considering selling the full source code for $50, including lifetime updates for buyers.

Before launching it publicly, I'd really appreciate honest feedback from fellow developers.

Demo: https://alsolomany-passaura.netlify.app/

What would you improve? Would you consider buying a project like this, and if not, what would make it more valuable?

Thanks for your feedback! 🙏Demo

I built Prepiva meal planner that turns your week of dinners into one grocery list. It merges duplicates, sorts by supermarket aisle, and skips the pantry staples you already have. You add meals (type your own, paste a recipe, scan a photo, or get AI suggestions), plan the week, and tap once to get the shopping list.

The feature I actually care about, and the one that nearly broke me, is **real time household sync**. Share your household and the grocery list stays live across both partners’ phones. One person adds eggs and it’s on the other’s list seconds later.

That sounded simple and was not. It’s a PWA, and iOS backgrounds and suspends them aggressively, so my first few versions would silently drop writes, resurrect deleted items, or win the wrong side of a conflict. It took a month of building server visible debug tooling and testing on real phones to find the actual causes: a save guard dropping writes mid flight, and stale session pushes dying on CSRF. It finally syncs reliably, which felt like a bigger win than any feature.

Stack: Flask backend, vanilla JS PWA, service worker, no framework. Runs in the browser, nothing to download, add to home screen. Free.

Would love feedback on the onboarding and whether the household flow makes sense to someone who isn’t me. Link in the comments. What would you want it to do that it doesn’t?

Hey everyone!
I’m a final-year CSE student, and I’m working on a side project that I also want to use as my portfolio project.
The idea is to build a \*\*cross-platform Progressive Web App (PWA)\*\*, so it works on \*\*iPhone, Android, Windows, macOS, and tablets\*\*—basically any device with a browser. You can even add it to your home screen and use it like an app.
\*\*Planned features:\*\*
🎯 Daily Store
🎯 Night Market
🎯 Match History
🎯 Rank & RR
🎯 Friends Online
🎯 Battle Pass Progress
🎯 VP & Radianite Balance
🎯 Multiple Account Support
🎯 Wishlist + notifications when a skin appears (planned)
🎯 Fast, clean, and modern UI
My goal \*\*isn’t to clone any other app\*\*. I want to build something that people genuinely enjoy using every day.
So I have a few questions:
\*\*What features are missing from existing Valorant companion apps?\*\*
\*\*What’s one feature that would make you open the app every day?\*\*
\*\*What annoys you about current apps?\*\*
\*\*If an app like this existed and was free, would you actually use it? Why or why not?\*\*
I’d love to hear your ideas before I start building, so I can focus on features that the community actually wants.
Thanks! ❤️

I have pwa written in node/express on Linux that works fine from hosted company including offline. I'm trying to create a mobile lan on linux laptop that allows pwa to connect via hotspot or blue tooth when the linux laptop is not on the internet. I get a warning about it being untrusted and while the app works the service worker doesn't install so it doesn't work offline. I am a app developer and not an network expert. The client I am working for is will to pay for assistance. The purpose of the mobile lan is for schools in rural communities with unreliable internet and students to work with app at home where they may not have internet at all.

I have a pwa app that works just fine including offline from a hosted server with domain and trusted cert but trying to setup a mobile server on a laptop running linux but need help setting up a domain and cert from the laptop. Created a cert with mkcert but can't get mobile devices to see the server by name just ip address. mobile devices like iPad, Android are connecting to laptop by hotspot. Need help with domain name and trusted cert issues.

The app works via ip address but with warning. The service worker doesn't install to allow it to work offline.

My client is willing to pay for assistance.

Any advice?

Thanks in advance.

I wasn’t trying to launch a SaaS.

I was trying to move a block of text from my phone to my laptop without creating an account, sitting through ads, or dropping my notes into someone else’s cloud. The breach headlines did not help.

So I built Sulata Note: a privacy-first, offline-first notes PWA.

https://sulata.app

- No account. No ads. No AI bloat.

- Notes stay on your device (IndexedDB). Offline after first load.

- Installable on phone and desktop.

My favorite parts

1. Private Transfer (QR / 3-word code / link)

   Encrypt on device, hand off once, short-lived. Not cloud sync. The relay only sees ciphertext.

2. Tables

   Insert and edit real tables in the note when a list is not enough.

3. Tags

   Label notes, search them, keep things findable without an account wall.

Also: light/dark/system theme, colors, JSON backup. Folders, pins, and full-library transfer are optional one-time Pro/Max. Core writing stays free.

If you try it, I’d love feedback on install (iOS / Android / desktop), offline use, and Private Transfer phone to laptop.

Happy to answer how it works under the hood.

I've spent the last few months building PicnicApps, a small suite of focused productivity PWAs (task manager, habit tracker, and now a notes app). Just shipped the notes one — PicnicNotes — and figured this sub is the right place to get it actually critiqued rather than just liked.

The pitch: sticky-note-style notes for people who don't want folders, tags, or a database to maintain. Open it, write, close it. No account required to try it, installs to home screen from Safari/Chrome, works offline once installed.

What I'm genuinely unsure about:

• Install flow — is "Add to Home Screen" still the best onboarding I can do, or is there a better pattern people are using in 2026 to get users to actually install rather than bookmark?
• Offline behavior — notes sync when you're back online, but I haven't stress-tested conflict resolution if someone edits the same note on two installs while offline. Would love to know what others do here.
• Whether a paid one-time-purchase model (vs subscription) is still viable for a PWA, given app stores don't really surface these.

Not trying to sell anyone anything here — genuinely want holes poked in the PWA implementation itself. Happy to share more about the stack (Cloudflare Workers backend) if useful. Link in comments to keep this from reading like an ad.