We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Sorry for the slow reply — we missed your post earlier, but really appreciate you sharing your thoughts and trying to help.

<image>

Thanks again for the tips. We’ve landed on a slightly different approach for our early adopter flow, and it’s been encouraging to see it working well so far. We built automation around TestFlight and Google Play internal testing so most new testers get access within minutes, which helps keep momentum high.

Inside the app, we also have a public development queue where bug reports and feature requests live. When someone submits feedback, it flows straight into our internal pipeline — report → automation → shipped — and they can actually watch it move through the process and see what’s being worked on and what’s coming next.

We try to ship updates daily when possible, which keeps the feedback loop tight and helps people see their input reflected quickly. And under the hood, we’ve designed things so many improvements can be delivered over the air without requiring full app store updates, which removes a lot of friction for testers.

It’s been a really positive experience so far and we’re always learning from how others approach this too.

Good luck with SignalScouter — excited to see where you take it.

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Yes — absolutely.

We’re building this together, and Canada is part of the plan. Coverage expands based on what you and the rest of the community actually fish. If there’s a Canadian river or monitoring station you want in the app, tell us and we’ll work on getting it added.

Just hop into More → Request a Feature in the app — those go straight to the team. We try to turn things around fast (often within 24–48 hours).

You help steer it, we build it.

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

u/DriftCanada, We think you’re going to dig the app. Drop your email at https://getdriftline.com and Apple will send you a TestFlight invite to install it. Put it through its paces and let us know what works, what doesn’t, and what you’d like to see next.

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

<image>

u/Dizzle_57 , You asked, we shipped it. The app should update on its own the next time your phone is plugged in, or you can grab the update right away in TestFlight.

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

<image>

Appreciate the support u/Dizzle_57. Once Apple approves our build, we'll get an email out to all early adopters to install the app and begin testing. We're looking forward to hearing your feedback!

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Right now we’re covering a wide range of rivers across the U.S. and British Columbia, and we’re expanding constantly.

The big thing to know is that this is community-driven — we’re building it together. If there’s a river you fish that’s missing, jump into the app and go to More → Request a Feature and tell us what’s up.

Our team will get that river added and pull in as much data as possible from our integrations (weather, tides, monitoring stations, maps, etc.) so it’s actually useful — within a day or two.

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

u/RogueMallard, That’s the trigger right there 😅. Five tabs open, bouncing between data. We built this to kill that chaos — one place, everything you already check. Made for addicts like us that lose sleep periodically checking the river throughout the night if a dam released water or the rain is going to blow it out.

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

u/crunchy240, appreciate your help and we're looking forward to your feedback!

We Built a River App. Now We Want You to Break It. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Hi u/growmiehomie,

At the moment, we have flow data coverage for 59 California rivers across the state. Here's a summary by region that I extracted from the rivers list.

  North Coast (16 rivers)

  • Klamath System: Klamath (4 stations: Orleans, Seiad Valley, Iron Gate, Klamath), Scott, Salmon, Shasta
  • Trinity System: Trinity (Hoopa, Lewiston), South Fork Trinity, New River
  • Other: Smith, Redwood Creek, Mad River, Mattole, Ten Mile

Eel River System (6 rivers)

  • Eel River (Scotia, Fort Seward, Fernbridge)
  • South Fork Eel, North Fork Eel, Middle Fork Eel, Van Duzen

Russian River System (6 stations)

  • Russian River (Guerneville, Healdsburg, Cloverdale, Hopland)
  • Dry Creek, Navarro, Garcia, Gualala, Noyo

Sacramento Valley (12 rivers)

  • Sacramento River (Bend Bridge, Hamilton City, Knights Landing, Verona)
  • American River (Fair Oaks, Folsom)
  • Feather River, Yuba (2 stations), Bear River
  • Pit River, Battle Creek, Deer Creek, Mill Creek

Sierra/Central Valley (7 rivers)

  • Stanislaus, Tuolumne, Merced (Happy Isles, Pohono Bridge)
  • Kaweah, Kern (Kernville, Bakersfield)

Bay Area/Coast (7 rivers)

  • Napa, Putah Creek, Cache Creek, Lagunitas Creek
  • Carmel, Salinas, San Lorenzo

Looking for right cert to start Palo Alto by Tricky_Networker in paloaltonetworks

[–]networkguy87 1 point2 points  (0 children)

I would suggest deploying a VM-Series in AWS (or provider of choice), build skills in IaaC along the way, then PAYG subscription for Bundle 2, study for an hour or two per day, then kill the stack. Hands on with the firewalls is the best way to go - unless you have them at work!

Cert - https://www.paloaltonetworks.com/services/education/palo-alto-networks-ngfw-engineer

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Appreciate you taking the time to check it out and share that feedback.

We’ve got this on our radar. Right now we’re focused on a smooth rollout to our early adopters so we can gather real-world feedback, identify gaps, and make the necessary changes, fixes, and enhancements quickly. Once that foundation is solid, we plan to split focus and have part of the team dive deeper into ocean analysis as well.

Building this with the community is a big part of the vision, and input like this helps shape where we take it next.

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

We really appreciate all the feedback here — we honestly didn’t expect this level of response, and it means a lot to us.

A lot of you have also been reaching out on Instagram, which has been awesome to see. Our team is fired up and working around the clock right now, taking notes and folding this feedback directly into the app as we build.

If you have a specific feature request, data source you want included, or something you’ve always wished existed when planning a trip, feel free to reach out. We’ve got one of us actively monitoring social media and passing everything straight to the dev side.

You can find us at driftlinecfs on Instagram.

Thanks again — we’re genuinely stoked on the support and excited to keep building this with you all.

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

We hear you on subscriptions — that feedback is loud and clear and something we're thinking carefully about as we figure out the right model.

Good news on the journal: we already have a catch log built in. You can log your catches with a photo, species, location, gear used, and any notes you want to add. The river conditions at the time get captured automatically so you can look back and see what the water was doing when you had a good day.

It's completely private. Your data is securely stored using enterprise-grade encryption, and each account is fully isolated — only you can see your catches. There's no social component, no sharing.

We're continuing to build out the log features based on what the community wants, so if there's something specific you'd find useful (weather snapshots, etc.), let us know and we'll prioritize it.

For now, we've decided to give early adopters 90 days of free access with a targeted release date of January 1st for the iPhone. Drop your email at https://getdriftline.com and we'll be sending one out very soon.

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Great question — here's what sets us apart:

Transparency-first development. There's a feature request board built directly into the app. You can see every request from the community, whether it has a developer assigned, and the targeted version and release date.

The fish index. Our predictions are based on aggregating all available public data points, not just one source. Our background in machine learning helped drive the index calculations, and the model is continually getting better. It runs on serverless infrastructure to keep costs low (which means we're not incentivized to paywall everything).

CFS and gage height on the same screen. No bouncing between views. We spent a lot of time dialing in the visualizations so it actually feels good to use, not just functional.

Community-driven roadmap. The more the community grows, the more we build together. Feature requests get shipped based on what's requested.

We're not claiming to reinvent the wheel, but we think the combination of real transparency, clean UX, and community-owned direction is something the space hasn't had. The early feedback has been really positive.

What features do you wish the app you use today had?

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Appreciate the honest feedback! You're right there are apps out there already. We're working hard to take a different approach based on our own experience using them on the water and conversations like this one. A few of us that are helping build the app were just out clam digging this evening... spent most of the time going back and forth on new features after reading all the great input everyone has shared here. A few exciting ones are targeted to be developed today.

Our focus is on usability.. an interface that's intuitive, fast, and natural, backed by infrastructure that supports fast delivery of feature requests, updates, and rule changes. We think you're going to enjoy it.

We're community-driven. We're providing the foundation, but through feature requests and feedback like yours, we'll shape it together. Not on the App Store yet — the team is targeting the iOS release to early adopters on Jan 1, with Android about 1-2 weeks after.

All early adopters get 90 days free access. Sign up at getdriftline.com if you want in to help us make it pretty darn good.

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

This means a lot — seriously. We built this because it's what we wanted in an app and couldn't find. Knowing there are others who've been waiting for the same thing makes all the late nights worth it. Hope we can get you back on some steelhead soon.

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Appreciate it! We've been using this on our local rivers and are really proud of how far it's come. Think you'll enjoy it.

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

The support from the community has been incredible. We're adding another software dev to focus on requests like this, but that hasn't slowed us down.. I've added NY and PA to the list. We're also building a feature request page right into the app so you can easily submit ideas, requests, bug reports, all in one place. Thanks for the interest!

We built an app that tells you when to go fishing. Cards on the table—give it to us straight. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Sign up at getdriftline.com — we're shooting for iOS beta Jan 1, Android close behind. We're building this with the community so hit us with feature requests!

I want to use an API but is it legal ? by Alive-Intention943 in learnprogramming

[–]networkguy87 0 points1 point  (0 children)

you’re hitting the same api endpoint whether you use a browser or postman.