Here's my 2 cents. This is a very difficult market to crack. On one hand you have Pinterest which is littered with individual trip guides and most likely your early adopters to generate content. However, they are NOT the right consumers to spend money on this.
Figure out the right niche in this market, it's very sparse!
Is there an app that suggest "Popular places near your route" while I'm planning a day? Or not just popular, but spots that've been mentioned in e.g. Lonely Planet, or some travel blog (sourcing the data would be a fascinating engineering exercise). It'd be great if the app recommends a spot, and when the user clicks "Squeeze it in", it would adjust the times accordingly. Or using your example of Tokyo, if I'm booked to see a Sumo match at 2 pm, and there's not enough time beforehand to squeeze it in, the app could even suggest an alternative time. (Hah this is turning to a travelling salesman problem...)
Yeah yeah, "popular" equals touristy, but just like Pumpkin Spice Latte in September, maybe I don't mind being a "basic tourist".
When Instagram's API was more open, someone did a heatmap of places that are tagged a lot in photos.
Nice! Traveling can be overwhelming. This is another great tool folks can use to help prep for their trip [since it's a CLI your market will naturally be developer focused]. I built https://trrip.co - much less about search and google maps, and much more about sorting itinerary in a chronological way. Both can coexist!
Kudos! This is a great project. I have one bone to pick, though. Had a show stopper issue a few months back with capacitor and the entire Ionic team was unresponsive, even on github. The issue was sending cookies to the server. Cookie would get set on the response but subsequent requests would not include the cookie. This was extremely aggravating and I had to halt my development. Relevant Github issue: https://github.com/ionic-team/capacitor/issues/1373. Would be great to know if a solution was ever found.
I used Ionic for 2 projects a few years back. Support on GitHub was, frankly, crap. I can sympathise to some degree, because they were still trying to figure out a commercialisation model, but they were far more interested in shipping new stuff and breaking things than actually stabilising what they already had. Major bugs affecting lots of people were ignored forever or closed without comment. It made for a horrible dev experience, and I honestly can't see myself touching it again with an extra-long barge pole.
Sorry about that, we definitely had some growing pains given we were a team of < 5 on the OSS side with a user base in the millions. Tried to automate as much as possible on the github side and over-applied our issue robot. I think our process has improved quite a bit recently and hope you give us another shot!
My main problem with Ionic (having used it for several apps) is that it is very difficult to find answers to question on the web. Reference sites are full of "this is how I fixed it" that work on v1 or v2 or v3 and most of all don't work for v4.
Unfortunately the speed in which they are changing things make community references obsolete quickly.
We hear you. This is why we moved to embracing core framework tooling like in Ionic 4 with Angular, where you don't need to go through our custom Angular build tooling which was a big source of issues and made it hard to get help.
Interesting, although true none for the current version, in my case a working solution has nearly always been in the top few results, even if it's originally from an older version
It took me a couple days but I put together https://bitsofempathy.co to create a space for talking about things like loneliness, relationships, family, and career. It's less about giving advice and more about showing empathy. Surprisingly, that might just be what we need in order to solve our own problems. Hope this can help someone. Would be grateful for any feedback as well.
Thank you! Happy to hear someone was actually reading that. The experience with using Medium Series as an author was not very pleasing to say it the least.
Interesting, that's really useful. But, assuming I have MagTek connected via USB to the computer, how does this code "listen" for the swipe? It looks like it can handle parsing the data just fine, but my question is how to get the data from the swipe into the javascript for parsing
The MagTek reader acts as a USB HID (aka a keyboard). When the cursor focus is put on a text field and you swipe a card, the MagTek device acts as if someone typed each character into the field. Then the javascript detects that and parses it out
Here's my 2 cents. This is a very difficult market to crack. On one hand you have Pinterest which is littered with individual trip guides and most likely your early adopters to generate content. However, they are NOT the right consumers to spend money on this.
Figure out the right niche in this market, it's very sparse!
Source: I'm the creator of https://trrip.co