Certain smartwatches offer a "pebble mode" feature like the Xiaomi band 9, you can get a keyring case for it and just attach it like that. I don't think it has automatic switching between exercise modes just tracking for steps etc.
Thanks. I don't want a smartwatch (I have a great "dumb" watch that I love). I'm rather looking for a device like this Air Lab but for physical activity.
A fan chiming in. I'm really happy someone someone is tackling this and it's looking good. One thing: can we get a demo instance just for initial snooping? A screenshot or two is fine but to get a feel for features it would be nice to have something (even heavily limited) we can just interact with?
That's the first thing I'm going to do as soon as it's possible! I recently refactored the code base to a monorepo, and still need to make some adjustments so it'll run stable again. Stay tuned :)
Whoop targets a pretty solid demographic of people who seem to want an auxillary training coach (the app tells you when to go to sleep) and don't want a typical smartwatch experience.
I'm not sure where modern smartwatches stand in terms of accurate readings but if I remember correctly it is still a minefield of inaccuracies. A watch for 50 dollars will _probably_ not do as well at reading your vitals as a watch for 200-500 dollars. Given Whoop markets itself as backed by science and seems to take the lead in studies on accurate heart rate readings[1].
Couple the above with great marketing and a decent kit of software and you have a difficult champion to dethrone. Hardware is expensive, marketing is difficult, a good app is hard to make, and putting together all three at once _while_ fighting a niche market is a struggle!
While 30/month can be difficult to swallow for someone that runs or swims as a casual hobby, someone that already pays hundreds a month for equipment, coaching, gym memberships, can have an easier time justifying it.
I'm not sure how I feel about the take on "disappearing pillars". I think that knowledge and expertise in the different "pillars" the author describes has become easier to access, reducing the moat around the individual pillars and allowing greater overlap between professions. So while you might not need a "sales team", you do need "sales knowledge". Cloud solutions are amazing until they are not and you need "infra knowledge" to understand where you are going wrong and to evaluate potential solutions.
I would argue that at a given size, scale, and growth you would find yourself looping back to the "original pillars".
The example of Neartail[1] competing with Shopify is a prime example of this. Shopify has a large market cap, shareholders demanding profits, a large quantity of paying customers. Neartail has none of these, it may have paying customers and it may have some potential in the future but it is currently all within the sphere of control of a few individuals.
Obviously a lot of what I'm saying is self-inflicted, you don't _have_ to grow endlessly but if you _do_ you need many decision makers and domain knowledge simply starts to reach limits for individuals (even when using AI).
The market for TODO list apps is 1 for every person in the world, everyone has a slightly different subjectivity and therefore has a slightly different optimal experience when it comes to TODO lists. Subjectivity is formed over time and through the course of events, therefore the market for TODO list apps is 1 for every person in the world for a given timeframe.
It's an obvious hyperbole but I think it stands to show that, in a similiar fashion, there is a reader (and by some aggregation readers plural) for everything you might think of writing.
How to get started with web development in 2025? What is ray-casting? How to emulate a piece of hardware in <language>? What I had for dinner tonight!
It may not be that everything is viral or a hit but you should find that most of the content you right will resonate with _someone_ and potentially help multiple _someones_.
Sometimes being satisfied with that 10-100 readers is all there is to it.
I've had good success teaching markdown to a fair few non-techie people. At the end of the day it better serves as a machine-readable middleground between a user-facing WYSIWYG (markdown-powered) editor and the server responding to it.
The difference here might be the rather huge gap between putting together a solid "blog post" and a solid "paper" on a subject. I agree these "types" of essays are difficult to challenge and given the sheer length of this post, it is also not accessible to _discuss_. I understand the desire to write about a topic extensively and how intimidating it might be to do so in a "scientific" way, this seems to be the middle ground. Maybe it's a seed for the author, or someone else, to develop further.
