From the viewpoint of a sharer, everything you share are currently public, it’s there to be discovered, you share them with the world and people nearby.
From the viewpoint of an explorer, someone who wants to know more about the world, you can pan to any part of the world, see what’s happening in that location, what people are sharing.
From the viewpoint of a local person, you have the opportunity to reach people nearby, whether it’s a cause, or just a happy moment you want to share, similarly, you get notifications from nearby.
From the viewpoint of an introvert, at the “More” section there are native social features for movies, tvshows and books, I’m personally very fond of the tvshows feature
I tried to shape Geobird for many use cases, at this point, only time and feedback will tell whether I was successful.
About the Journey;
Started 4 years ago, I’m not proud of how long it has been, launched in the 1.5th year, fixed bugs, improved the backend significantly with first users until the 2nd year, launched the mobile apps around the 3rd year and here we are, a lot of iterations later (originally intended 4 years to be 6 months, lol)
Initially intended building geobird with a team, tried to recruit a designer friend I knew, failed, decided to build a prototype myself and extend the team later on, I’m glad I initially failed being a company (of people), if I built geobird at a company scale, my funds would be almost exhausted by now - but being a one person operation, I can keep on failing for years, keep the product alive forever and only grow in case widespread adoption ever happens
I would appreciate any kind of feedback and criticism,
+ Ask me anything,
Currently the game is too complex, so it's not satisfying for an average user
It might be a good idea to turn it into a game where it starts easy, gets harder, and you can share the level you achieved and brag about it (like 1 2 3 4 5 6 7, the level could be stored in localStorage so a user can continue fresh from that same level later on, with a different random pieceset)
Edit: Just checked the code, impressive :) - I assumed the game and pieces were randomly generated
great to hear, I've been meaning to use Spreedly/core almost a year now, but didn't take the payment step yet.
It would be interesting if subscriptions were also in Spreedly Core, but I can't imagine how it would work, I guess spreedly core could ping the servers of the customer if the CC failed or expired, but I guess it's unnecessary since an effort is always required in that case, so building the subscription logic on the code seems logical.
I haven't used spreedly core yet, but I really like the team, they always answer emails and help around payment topics, can't wait to solve gateway problems and start using spreedly