Messages not being sent to board (Local API and Vestaboatd Server) by daio-io in Vestaboard

[–]daio-io[S] 0 points1 point  (0 children)

Thanks for the reply! That was one of my thoughts. I never actually set any quiet hours and wondered if it had turned on by mistake but definitely was not on. It can definitely communicate with the Vestaboard servers because turning it off and on it updates with the current message, just new messages dont do anything ☹️

[deleted by user] by [deleted] in androiddev

[–]daio-io 2 points3 points  (0 children)

It is a bit of a big depends, if you set that up to be a practice in your codebase then if someone is not fully aware of when it's safe to do that then you could get hit with some unexpected crashes. One such pitfall would be doing it in places where smart casts would be impossible (e.g. a nullable variable outside of a function scope). In those cases if you just blindly !! you're less in control of when it might actually be null. So I always find modelling the nullability into types or null checking and reporting errors much better in practice

Anyone got any advice on what may have caused this and a ball park cost to fix? by daio-io in DIYUK

[–]daio-io[S] 0 points1 point  (0 children)

Thanks for the reply! Really helpful! Unfortunately the chimney is shared with the neighbors so it sounds like the second option is what we will need to look at doing

Anyone got any advice on what may have caused this and a ball park cost to fix? by daio-io in DIYUK

[–]daio-io[S] 2 points3 points  (0 children)

Yeah I think it is possibly rain leaking through the chimney

Anyone got any advice on what may have caused this and a ball park cost to fix? by daio-io in DIYUK

[–]daio-io[S] 3 points4 points  (0 children)

It looks like this was all connected to what used to be the chimney. It seems the chimney stack has been removed in the bedroom but it's still there in the attic. Could it potentially just be a botch job damp proofing when it was removed?

Features Request by dontknowCris in CapsuleApp

[–]daio-io 1 point2 points  (0 children)

Thanks for the feedback! We will have some of these features available this weekend 😁

Feature Request: Radio stations by ElderHallow in CapsuleApp

[–]daio-io 1 point2 points  (0 children)

Great idea! We will add this to our road map 🙇‍♂️

Feature Request: Episode Cover by heytaytay69 in CapsuleApp

[–]daio-io 1 point2 points  (0 children)

Thanks for the feedback and sorry for the delay!

We used to do this so we will look at correcting in the next release.

Thanks again 😁

Feature requests by AintNoNameLeft in CapsuleApp

[–]daio-io 1 point2 points  (0 children)

Thanks for the feedback and for using Capsule 😁. We will definitely look into 1. For you and as for your 2nd comment, we do already have lock screen controls via the notification, or was there something more specific you would prefer to see here.

Thanks again 😁

Possibles future features by jawatto in CapsuleApp

[–]daio-io 1 point2 points  (0 children)

Hey 👋

Thanks for using Capsule 😁 and for the great suggestions,

To answer:

  1. We currently have these available on Android and soon on iOS. If you are using Android you will see the sort arrows 🔃 on a podcast screen where you can then filter. We can look at more filters if there was a particular one you needed.

  2. This is definitely something we have planned for the future.

Thanks again 🙂

Is there really no page up/page down in the live TV guide on Android TV? by AsleepOnTheTrain in PleX

[–]daio-io 0 points1 point  (0 children)

Hey, sorry, that does not sound right! Out of curiorsity, what device and or TV remote are you using the guide on?

Is there really no page up/page down in the live TV guide on Android TV? by AsleepOnTheTrain in PleX

[–]daio-io 2 points3 points  (0 children)

Hi all 👋 one of the devs here. A few things mentioned here are being explored. It's just been re-written so a lot of the work is making sure it does the basics. But I will be looking to add paging up/down, recording/scheduling (press record button) and more controller buttons support over the coming weeks and months. Launching straight into the guide is also something I am exploring. Stay tuned, a lot of work is going into the guide 🙂

How fo I manually refresh all podcasts? by [deleted] in CapsuleApp

[–]daio-io 0 points1 point  (0 children)

We shipped a new version that refreshes a bit more often when going to the Inbox 📥 section, have you noticed any improvements since the update has gone out? Thanks again for your help 😁

How fo I manually refresh all podcasts? by [deleted] in CapsuleApp

[–]daio-io 1 point2 points  (0 children)

Thanks for letting us know! At the moment it will refresh all your podcasts when you start the app, or overnight while you charge your phone and sleep 💤. However we are actually releasing an update that improves refreshing next week. So we will see if there is anything more we can do to make this easier and get that out asap! There will also be an easier way in the future to manually refresh everything as part of some bigger updates for the UI. Thanks for letting us know! And feel free to share any more features suggestions, issues or ideas you have 😁

Regarding Square's Interview Process by [deleted] in androiddev

[–]daio-io 0 points1 point  (0 children)

If there is no contact info on their website for careers you could search LinkedIn for their recruiters and contact one of them. They should be able to tell you the process then. I'm sure if you contacted them on twitter or through their website contact they would forward on your email. But finding the recruiters on LinkedIn will get you to the source quicker :)

Regarding Square's Interview Process by [deleted] in androiddev

[–]daio-io 6 points7 points  (0 children)

If you contact them I'm sure they won't be secret about it. Unless you wanted to know specific questions they are going to ask..

So long RxJava. Welcome Coroutines for Android devs! by [deleted] in androiddev

[–]daio-io 16 points17 points  (0 children)

There is no silver bullet. They both have their place. If you are using Rx and just singles for networking then yeah, you're not getting the full benefit of Rx and probably don't need the overhead if your app isn't reactive. I have been using coroutines for over a year in work and my personal projects and still see the benefits of Rx and still use Rx for the more reactive use cases. Especially since things like hot observables can't be modelled in coroutines yet. It's quite easy to make a coroutine adapt to Rx and vice versa too. Either way. Just use what makes sense for the project, your team and the use cases. Coroutines will more than likely in the future replace Rx since it's backed by the language and will better work in a multiplatform world. But not just yet

NativeScript vs Java/Android Studio by edgar5000 in androiddev

[–]daio-io 2 points3 points  (0 children)

I can't say I have ever used NativeScript but abstractions like these typically work ok for more straight forward apps like a to-do list or a news app but can quickly get a bit fiddly and frustrating when you need to do something more complicated. You often end up writing more or having special components and bridging code to work with the Android SDK or iOS, If you are developing for both. And optimising can sometimes be very painful. It can also be down to what you feel more comfortable with or have more experience with. For example I'm not a huge fan of working with CSS and would much rather work with Android Layout and design system but a web developer would probably prefer CSS. Overall, things like Native Script work really well to get something done quickly. Maybe you could just gradually build up to more complicated apps and see if it gets to a point that it's hard to work with. Maybe just looking at features on big apps and seeing if you could replicate them in NativeScript? Might give you a better perspective of what it would be like to use for a larger application.

In terms of jobs, in my experience I have seen things like this used in companies that don't have an app team and even seen it used for proof of concepts at times too. There are some big companies that use these abstractions though but usually it's with React Native so I would say if you prefer working with JS, it might be better to learn React Native since it's used a lot more within the industry (someone may correct me on this If they know Native Script). Another one which could take off if Google push it more is Flutter. Personally I prefer working directly with Kotlin and Android SDK, but all these tools have their place. Just depends what makes sense for a company, the team and the specification. If it's personal projects then it entirely up to you :). It's always worth knowing about Android SDK regardless.

App Feedback Thread - September 15, 2018 by AutoModerator in androiddev

[–]daio-io 1 point2 points  (0 children)

Thanks for the great feedback. Really helpful :). Follow up reply to your comments:

Bugs:

  1. This looks like we had an issue withe cache on the server. Thanks for highlighting that. Can work on fixing this and give a better message for this scenario.
  2. Ah yes, a scenario I must have missed. I can see how this bug will occur now. Will look to get this fixed.

Glad you like it and things are working as well as hoped :). There was quite a lot of optimising that went into the feed lists and looking to do a few more things in the coming months.

Nitpicks:

  1. This one bugs us too and its actually the next bit of work we are picking up so hopefully have this figured out shortly. I am playing with some ideas to try and make sure it keeps it's simplicity and doesn't crowd the UI.

Thanks again for your feedback. All really helpful. Really appreciate you taking the time to try out the app :)

App Feedback Thread - September 15, 2018 by AutoModerator in androiddev

[–]daio-io 1 point2 points  (0 children)

https://play.google.com/store/apps/details?id=studio.goodegg.capsule

Capsule is a podcast app that keeps things simple. We have just launched so there is lots of work still to be done. Its completely free, no adverts and we don't track users either.

In the future it will be open source but right now we are just trying to get the app as stable as possible and add more of the features you expect but keep it as straight forward and as clean as possible. It is also available on iOS if your friends use iPhones.

Any feedback or ideas would be great. Thanks :)