Aleksandr

Results 30 comments of Aleksandr

Hello, Right now, this app is all about sending SMS. Receiving wasn't in the original plan, but I'll give it some thought. Thank you for your suggestion.

Good news, everyone! I'm delighted to announce that the application now includes the capability to send webhooks when new SMS messages are received. This new feature is available for you...

Currently, the backend doesn't support SQLite, and I don't have plans to add SQLite support in the short term. However, this might be considered in the long term if there's...

I think the most straightforward way to implement this would be to expose settings via an API. This would allow you to simply `GET` settings from one device and `PUT`...

Let’s separate these into two distinct features. ### **Webhooks UI** Yes, I’ve already planned to add a read-only UI for webhooks. The primary purpose of this UI will be to...

Hello, Thank you for your feature request. I've added this to the backlog. The current plan is to address this as part of a future SIM management API, which would...

Hello! Thank you for your proposal. Unfortunately, the current version of the app heavily depends on Firebase Cloud Messaging (FCM), which is part of Google Play Services. Since Google Play...

Hello, @pepper3k 1. The justification is straightforward: it was the simplest solution for the first version of the app. FCM doesn't require any external dependencies and is supported by a...

@hasan-4 You're not the first to ask about WebSocket support. This feature is already on my backlog, though it's not currently a top priority. The main challenge with any always-online...

@hasan-4 , Are you referring to implementing a user-facing WebSocket API? In our previous discussion, WebSocket was primarily considered for device-server communication as an alternative to FCM. A user-facing WebSocket...