Originally Posted by
Xandrios
Awesome project, happy to see this being developed in a way that looks this polished and professional!
Are you planning to make this into a paid service (Noticed a few references to it being Free), i.e. this becoming a commercial venture rather than a hobby project?
Just signed up and noticed a few things. Many minor things, just listing what I noticed. Absolutely not criticism either - like I said, very glad to see something like this being built - so this is just to aim at improving even further.
Wow, thank you so much for this incredibly thoughtful and detailed feedback! This is exactly the kind of input that helps make SkyStatus better. I genuinely appreciate you taking the time to write all of this down.
To answer your first question upfront: no, I don't see myself as the Mark Zuckerberg of Flying Blue 😄. There are no commercial plans whatsoever. This project started as a personal itch to scratch and has completely spiraled out of control. But I'm having an absolute blast building it. If others can benefit from it too, that just makes it more fun. It's pure passion, nothing more.
Now, let me address your points:
✅ COMPLETED
Privacy Point 1 - Local Mode confusion
Clarified! The three modes (Account, Local, Demo) are now properly explained throughout the app and documentation.
Privacy Point 3 - PDF handling transparency
Added clear documentation: PDFs are processed entirely client-side in your browser. The file never leaves your device. Only extracted flight data (routes, dates, XP) is stored if you have an account. Personal details like name and FF number are never transmitted or stored.
Privacy Point 4 - GDPR compliance
Done! Privacy Policy and Terms of Service are now compliant and clearly accessible (directly from the PDF import)
Functionality Point 1 - Browser password autofill
Fixed! Added autocomplete="new-password" to the signup form so browsers properly suggest random passwords.
Functionality Point 4 - User-defined CPM for miles valuation
Implemented! There's now a "How do you value a mile?" section in the Miles Engine with preset options (Conservative €0.008, Average €0.012, Aspirational €0.018) or you can set your own target CPM. All portfolio valuations are calculated based on your personal target.
Functionality Point 6 - Manual cabin selection per segment
Done! You can now adjust the cabin class for each individual segment when entering multi-city flights. So for LIM-AMS-ATH, you can set the long-haul as Premium Economy and the short-haul feeder as Economy.
🤔 OPEN - NEED TO THINK ABOUT
Functionality Point 2 - Copy/paste import from FB/KL/AF websites
Interesting idea! Would reduce the need to upload PDFs entirely. Need to investigate what the copy/paste output looks like and whether it's consistent enough to parse reliably.
Functionality Point 3 - TripIt API integration
Love this idea in principle. The challenge you mentioned (inconsistent data formats) is real. Could work as a "starting point" import that users then refine manually. Added to the backlog.
Functionality Point 5 - Cabin availability database
This is tricky. There's no reliable public dataset for which routes have which cabins. Crowdsourcing from users is an interesting angle once there's enough data. For now, the manual per-segment cabin selector is the workaround.
Functionality Point 7 - Tax-adjusted mileage earning
Complex problem. Airport taxes vary wildly and change frequently. Crowdsourcing could work at scale, but we'd need significant volume. Parking this one for now.
Thanks again for the detailed feedback. It's users like you that make building this worthwhile. If you spot anything else, keep it coming! 🙏
