1,474 karma · joined May 8, 2011
The marketing aspect of the app would be key - the app store is crowded for convoy tracker apps - but hardly anyone is framing the "friends" angle. Good luck!
It used to be a thing of the past - people don't seem to bother now. Go ahead and create the profile. Search and connect with your colleagues.
https://news.ycombinator.com/item?id=38428497
https://news.ycombinator.com/item?id=38473489
It’s a good problem to solve - eager to try if you have a product ready.
For people interested in this area, I can also recommend "The Book You Wish Your Parents Had Read: (And Your Children Will Be Glad That You Did)" (author: Philippa Perry).
What's underappreciated, is becoming those fresh pair of eyes yourselves from time to time, to help others with ideas they can readily use. It hones own skills too.
As another comment mentions, support for Linux is a big plus - we need better GUIs in there.
There are numerous examples cited in the book and around the web on how this streamlines discussions (and also gives everyone a chance to chip in from different angles).
The UX is the plus here - I am aware that there have been several other apps that have offered a polished UX since then, but the convenience and my learned affinity to Soulver makes me keep it.
P.S. does the transit authority offer an API or is this prone to breaking when they change their page layout?
[edit: I just read about the rumor on your webpage. Clarifies.]
https://www.linkedin.com/pulse/beauty-amazons-6-pager-brad-p...
https://www.anecdote.com/2018/05/amazons-six-page-narrative-...
https://firebase.google.com/docs/firestore/rtdb-vs-firestore
Less than 99.95% but equal to or greater than 99.0%: 10% credit
Less than 99.0%: 30% credit
[1] https://firebase.google.com/terms/service-level-agreement/
Some more information here: https://www.toptal.com/xml/an-informal-introduction-to-docx
Taking the shopping cart example: "In a former life, I used to write SQL to extract customer of the week. Basically, select from orders table where basket size is the biggest."
The author decided that 'customer of the week' will be selected by 'biggest basket size'. Not by 'biggest $ amount spent', 'fastest time from add-to-cart to checkout' (and numerous other attributes or combination of them). This decision (the "best attribute") was taken by a human, leaving a field open where a combination of attributes could've resulted in overall better business outcome (how much did 99% of these retained customers shop for, in $ value over lifetime?, etc)
This is possibly what the parent commenter is hinting at - this human decision leaves a lot of optimization scope, where ML could have helped.