Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We're bringing Pebble back

repebble.com

Post reply on HN
Print view View original

501–510 of 758 posts

Re: We're bringing Pebble back

#501

Post by suddenclarity »

zem wrote: post #351
suddenclarity wrote: post #338

Earlier quoted context omitted.

> Why do no android phones have IR blasters anymore? Both Xiaomi and OnePlus have it on their phones. Personally I never used mine and didn't see the point. It was quicker and more effortless to just click the button on the physical remote next to me than having to navigate through the apps on my phone. > Or FM Radio support? You can listen to almost any radio station online nowadays and plenty of countries (EU) have…

well, more compellingly, why can't I get a phone with a physical notification light any more?! amazingly useful feature on my galaxy nexus from back in like 2012, but I've never been able to find another phone with it. not to mention a 5.5" phone with a flagship chip in it. I'll even forgo the camera quality.

I'm not very knowledgeable about current models but isn't that the whole USP for Nothing Phone? There are multiple lights so you can customize unique patterns for both contacts and apps.

Re: We're bringing Pebble back

#502

Post by khasan222 »

primozk wrote: post #418
seanhunter wrote: post #405

Earlier quoted context omitted.

Garmin is the perfect solution if you want a smart watch with a gps that takes 5mins to possibly sync 50% of the time and a touchscreen-only interface that doesn’t work if it gets wet or say sweaty. Ie during most of the activities it’s supposedly designed for. When I got a garmin smartwatch I was astounded by how poor the basic ux is in almost every single way. If I’m swimming, how do I stop my work out? The touchsc…

Which Garmin to you have? This isn't my experience. And you have option to buy Garmin watches with actual buttons, I agree the touch-screen only are useless.

Im not OP, but this sounds like the garmin instinct.

Re: We're bringing Pebble back

#504

Post by hobo_mark »

Guys, I am still running my P2HR every day.

I, like most of us I believe (and we are dozens :), am using it with GadgetBridge.

I wrote my own watchface for it, in C. Also wrote some automation that periodically exports and backs up my data off GadgetBridge.

I would like to keep using GB, but my aging P2 might die any time now (already had to replace the side buttons, the plastic disintegrated after a few years) and I have been looking for a replacement watch that allows exporting my sleep data into GB.

NONE of the hardware currently supported by the app appears to make sleep data available in the way Pebble did?!

Please make new Pebbles, and keep them compatible with GadgetBridge.

Re: We're bringing Pebble back

#505

Post by alexbouchard »

nym3r0s wrote: post #500

The primary use for a smartwatch for myself (and many of my family, friends) is fitness and health tracking. Card payments, notifications, WatchFaces etc. are all secondary. Basically what Whoop is doing with their strap - but minus the subscription model. I know a ton of people who tried the whoop but felt it was extremely pricey and didn't have the accuracy of an apple watch. I would be happy to pay ~$400-500 up fr…

From most watch market positioning I'd assume this to be true. However for me it's the exact opposite, the watch is a tool to cut phone use. All I care about is LTE and the minimum I need to get around the world. SMS, calls, WhatsApp, Gmaps. All existing decent looking watch have atrocious battery life to offer all the health features.

Re: We're bringing Pebble back

#506

Post by samastur »

dingaling wrote: post #448
akho wrote: post #423

Earlier quoted context omitted.

not the reader though

It's strange to see the naivety around Reader. If Facebook had created it, people would recognise the initiative to gate-keep, regulate and curate the Wild West of RSS. "They're trying to keep you inside their walled garden!"

Because we miss what Reader was and not what it could have become.

As a more prolific blog writer at the time I also liked that their bot would include number of people who were subscribed to my blog in their User Agent.

Re: We're bringing Pebble back

#507

Post by mrzool »

nym3r0s wrote: post #500

The primary use for a smartwatch for myself (and many of my family, friends) is fitness and health tracking. Card payments, notifications, WatchFaces etc. are all secondary. Basically what Whoop is doing with their strap - but minus the subscription model. I know a ton of people who tried the whoop but felt it was extremely pricey and didn't have the accuracy of an apple watch. I would be happy to pay ~$400-500 up fr…

> I would be happy to pay ~$400-500 up front for hardware that integrates with Apple Health and provides solid, reliable health tracking without a need for a subscription.

That price point would make it unaffordable for the majority of the world’s population. Shouldn’t we try and make health monitoring and fitness tracking more accessible? That was one of Pebble’s biggest benefits.

Re: We're bringing Pebble back

#509

Post by zevon »

sebstefan wrote: post #489

I'm guessing it couldn't possibly do navigation display for Google maps?

It displays notifications fine which I find helpful for navigation. There are/were also some more advanced navigation apps around. For example this one https://apps.rebble.io/en_US/application/52e7521679f937c1820... or this one https://apps.rebble.io/en_US/application/666e80ff7568f7000a0...

Re: We're bringing Pebble back

#510

Post by abcd_f »

scarface_74 wrote: post #262
abcd_f wrote: post #162

Earlier quoted context omitted.

Don’t know about Apple Watch development, but the scope of what you can do with Garmin's SDK is limited, apps run in a VM, ie no native code with respective performance issues and, as important, their developer support is a complete and utter garbage. It's a lucky day when someone from Garmin graces Forums with their presence and bestows few sentences they think could pass for an answer. In other words, yeah, the SDK…

You run native code on the Watch itself and most of the limitations are around not doing anything that will kill the small battery.

Nope, not native code.

> Monkey C compiles into byte code that is interpreted by a virtual machine, similar to Java.

https://developer.garmin.com/connect-iq/reference-guides/mon..., 2nd paragraph.

Post reply on HN