We'd definitely be open to licensing this out to other travel companies/startups, so do contact me at harry@travelchime.com if you know anyone who's interested
1,051 karma · joined September 24, 2012
We'd definitely be open to licensing this out to other travel companies/startups, so do contact me at harry@travelchime.com if you know anyone who's interested
There are 3 main issues raised:
- Getting users to learn a new tool is super-hard since users are used to being able to do anything and have custom workflows. That's why they use Google Docs or Word or Google Sheets
- Monetization with affiliates is OK, but you are in some ways competing with your customers (the OTAs), and they're still making more money and can outspend you on marketing
- Acquiring users is hard since users don't travel often, and the typical channels for infrequently-used product growth (SEO, SEM) are super-competitive
We really try hard to solve the first problem by not being prescriptive about how you use Travelchime. We try very hard to let users do whatever they might want to do in a Google Doc or Google Maps. Unlike many travel planners we've tried, we don't assume you like to plan minute-to-minute or by referring to a single resource. We've had hours of face-to-face chats with tens of users and we're not trying to flip the way they plan travel, but rather complement the way they plan travel.
For monetization, we have some ideas around it but aren't sure enough of them to share right now.
We also believe the user acquisition door isn't as closed as it seems. First, we're hooking onto a growing trend of travel being social. Most people we talked to have asked friends or family for travel tips, and we want to make planning based on that easy. Second, we've done this before, and while we know SEO is tough, Peter and I have built a profitable (albeit fairly niche) business in the field on top of SEO before.
I might be a bit deluded about this, but I'm OK with it!
We've also noticed the text being inconsistent. It's especially bad for foreign places. We've added it to our bug-list!
The itinerary inspiration lists honestly are kinda similar to the place list you create. For the place list you create, you can click on a place to see more info and links out. We'd like to merge the behaviour for those so it isn't confusing, but that's also in the pipeline. Sorry about that!
You're definitely not the only one who's requested a checklist, so we're looking into prioritizing that.
We've thought about a more calendar-focused view, where users can explicitly annotate: "this section represents a day" or "this event has a specific time" and would show up on the calendar. I can try to mock something up and see what you think.
I've bookmarked your profile page and we'll definitely reach out within the next week!
QuillJS has been working well enough for us as an editor! It supports the collaborative editing we need, as well as mobile.
I could write a whole essay on our whole decision-making on contenteditable controls. The short answer is SlateJS could be great, but didn't work well on mobile yet. DraftJS is kinda abandoned by Facebook, and Quill isn't native to React but still works well, so we used it.
Here's an older post I made on this subject https://news.ycombinator.com/item?id=18998042#19000425
Having worked in travel for a while now, we realize that paid marketing is incredibly competitive. Based on that understanding, we've actually never spent a single cent for paid marketing on our previous projects.
For growth: We want to just provide a really good central tool for people to plan their trips, and an easy way for those people to share plans with their friends. We think travel is inherently social, and that's something we want to do well (while respecting privacy).
For the idea of "day tabs" - we actually used to have a calendar view in the product, but stripped it out for this format of "lists". Currently, it's possible to get close to what you want by just naming the place lists: "Day 1" or "Day 2" - see https://travelchime.com/plan/grayuczaswflzvto
Would this work for you? Or do you like to plan hour-by-hour?
The place suggestions based on what you have make a lot of sense. There are 2 approaches we've considered for that: by doing Netflix-style "users who watch these movies go to these places", and using crawled data. Basing it off of user preferences does require a good amount of data and lots of care to ensure good privacy.
Because of that, I think we'll most likely start by expanding the range of pre-curated lists. There's tons of content on the web that we'd love to link out to for specific types of travelers: "best for families" or "best for adventurous" travelers. We can make that information easy to find and easy to incorporate into your own plans
How do you currently aggregate/split costs for the trip? Do you just use a spreadsheet?
Before Travelchime, Peter and I had some experience with monetizing via hotel and flight affiliate fees via our past sites, https://bookwithmatrix.com and https://alltheflightdeals.com . We did a bit of research, and about 2/3 of travelers who use docs start one before they book the hotels. We believe that if our recommendations are good enough (based on where you'd like to go in a trip plan), we could monetize using the same model there.
Forking an existing trip plan and copying bits/pieces from friends' trip plans are both features we'd really like to build out really soon! So many of my trips end up having 50%+ overlap with some of my friends, so that'd save a ton of time
I really do like the concept though - whenever I travel I do try to eat the regional specialties
If any of you have used Quill and Prosemirror, what were your impressions of the differences between the two?
Here's what I've observed so far:
1. DraftJS (React) works on desktop, but has no plans for collaborative editing, mobile support, and limited development. We found it hard to extend the paste handling for custom behaviours too. On the other hand, there are a lot of nice libraries built around it (we used medium-draft)
2. Slate (React) is definitely the way to go for React developers who don't yet need mobile support. It's mature and has a good community of developers. The one downside is that some of the popular plugins lost compatibility with the latest version of Slate, and some plugin maintainers (notably Gitbooks) have decided to stop tracking the mainline releases [1]
3. Quill (non-React) seems very mature with a good ecosystem of plugins. Instead of relying on React Components, it relies on there being a strict mapping between the DOM and the model that you build. The "model" is the DOM, so-to-speak, but with heavy restrictions to avoid ContentEditable issues. We've found it to be very mature, and it's the only one of the 3 we've found to have great mobile and collaborative-editing support out of the box. That was important for us, so we ended up using it today
Draft appears to be essentially somewhat unmaintained, whereas the Slate community has continued to be very active (thanks for the Android support! That's one reason we ended up using Quill for now)
The built-in copy-paste handling is pretty messy to extend compared to Slate, where the system of normalizers works a lot better.
After reading the article for about 15 minutes, I finally understand loeb and it's pretty cool! It's an easy way to actually run a list of lazy-loading statements (functions) in a way that all of them resolve to their eventual values.
That being said, it feels like the function is both too abstract to understand, yet not effective as an abstraction that I can apply to other problems. For a few contrasting examples, reverse_string is not a very abstract function, as it operates on a very concrete operand and produces an effect that's intuitive outside of mathematical theory. On the other end, a hash table is very abstract, but we choose to learn it because it's such an useful solution.
As for loeb, I only understand how to use it to create a spreadsheet, yet it's clearly meant for more than that since it's given such an abstract name. It's also not called evaluate_lazy_functions_on_operands either so it must be more than that too! Is there something I'm missing?
Note that these are educated guesses from their statement: "Heap’s data is stored in a Postgres cluster running on i3 instances in EC2. These are machines with large amounts of NVMe storage—they’re rated at up to 3 million IOPS, perfect for high transaction volume database use cases"
1. Aurora charges per-request ($0.20/million). Given that analytics comes with tons of events and that they wanted servers that have up to 3 million IOPS, it can get pricey fast.
2. RDS has database instances that have SSDs that provide "up to 40,000 IOPS" per instance in their provisioned case, which is probably not enough.
It strips down a subset of HTML that can then be used to render UI across different base platforms. I feel like it could be a good starting point as well
I believe it's currently used by Youtube to render its HTML5 app on many set-top box devices
We'll make a note of this! It does seem like a cool idea to put these 2 features together and automate the updating of API endpoints
As far as I know, it only sends URLs of your visits to its affiliates, but not for other sites
It is not a ruling on whether the US government can access other data stored by US companies abroad.
The original case started because Microsoft argued that the US Government has no right to access data stored abroad, because that would give unprecedented access to non-citizens' data. The government argued that it did.
If there were a simple-to-maintain herb garden hydroponics set, I'd totally be interested!
The fact that e-sports has exploded I think has a lot to do with how they've become more similar to real-world sports. We've moved from very artificial e-sports like Starcraft, fighting, racing (usually 1v1 games with extreme focus), to distinct role-based "MOBA" games like Overwatch, League of Legends that are much more similar to popular existing games like soccer and baseball.
Unlike in the earlier games, they rely slightly less than pure mechanical skill, which makes the sports accessible. They're team games with differentiated roles, allowing beginners a way into the game playing with, rather than against their friends. Sounds familiar? This could describe soccer, basketball, football, and all of the top spectator sports today.
Their only real substantial difference is that they're far more accessible, requiring only equipment that many already have (the games intentionally minimize system requirements) and don't require real physical athleticism.
I think it's no surprise they're becoming popular as spectator sports: they're building on a proven formula, but adding a dash of accessibility.
Thanks to feedback from the HN community, we realized it wasn't as easy to use as it should have been, so we've now added:
- A new interface (https://wrapapi.com/#/api) that's browser-like and easy to use.
- A more intelligent guesser where if you capture multiple similar requests, we'll automatically create inputs and parameters as needed.
Let us know what you think!
Here are a few really good articles:
- Why we should tax property by street frontage: http://urbankchoze.blogspot.ca/2016/07/city-taxes-as-urban-g...
- Advantages of one-way streets: http://urbankchoze.blogspot.ca/2016/03/the-case-of-one-way-s...
- Impacts of commercial density: http://urbankchoze.blogspot.ca/2015/11/commercial-or-residen...
Strongly recommend it! It's my favourite urbanism blog, although there aren't usually that many posts thanks to the long length and high quality
I think this is actually not a problem, because most users can still successfully find the answers they need on Stack Overflow.
Here's how I believe I and other users use Stack Overflow. We have a problem. We Google that problem (or occasionally search on Stack Overflow). We usually find a fairly popular (and high-quality) question with a fairly popular answer. We're satisfied by that answer.
The article points out that the number of good questions has remained constant, but the number of bad questions has increased. Maybe there's really a close-to-constant number of good, searchable questions that can be asked at any given time, and the declining average quality is just a result of Stack Overflow's popularity.
"There is a more fundamental issue at the heart of this seemingly good solution: A 10-year exercise window is really a direct wealth transfer from the employees who choose to remain at the company and build future shareholder value, to former employees who are no longer contributing to building the business/ its ultimate value."
In short, Kupor believes that even if you chose a lower-salary, higher-options/equity package, you should be stripped of your options if you leave. To him, it's only fair if only investors and employees who remain get to keep equity. Instead, you, who have been directly responsible for making the stock price rise so much that your options are costly to exercise, deserve nothing.
We've already tested it a bunch, but would love the HN community's feedback. If you find an itinerary that, when pasted into BookWithMatrix, gives an "Invalid itinerary" error message, we'll buy you a drink or send you $5!
It seems that the .col-[size]-[num] classes function exactly the same way in both.