garthvh
commented
1 year ago Hi Lukas, I am a part of the LLC the controls the Meshtastic trademark and am interested in things that move the Meshtastic project forward, I can easily be sponsored but to be honest I don't see proprietary branded forks as progress. Why would this this be necessary? You can find some legal and trademark information here https://meshtastic.org/docs/legal I would strongly encourage you to just contribute to the the project instead of creating a fork. Thanks, Garth On Monday, February 27, 2023 at 01:39:43 AM PST, buluk3214 @.***> wrote:
Dear Mr. Vander Houwen,
first I have to thank you for your work according to the Meshtastic-App. Great effort from your side!
Let me introduce myself and our company shortly: My name is Lukas Bucher, self employed since 2017. In december 2021 my IT-technician and me founded the company Jellynet GmbH. The company offers - beside optimization of biomass cogeneration plants - disaster protection for municipalities in Austria, Europe. Actually we are working on a failsafe variant of Meshtastic-application coupled with infrastructural transmitters.
My business partner/IT-technician developed an android-version of Jellynet/Meshtastic application with Jellynet-branding. This application works very well.
While some testing scenarios we detected some issues with the IOS-App. Unfortunately we are no specialists in programming IOS-systems, so that is one point why I am writing you.
-
One problem we detected was, if you go into the channel-chat (not in the single-chat) in messages, then go back to the message-overview, then you jump again in channel-chat, the app freezes/has issues with jumping in the channel-chat again.
-
Another issue we detected was, that the Meshtastic-device receives messages, but the IOS-App does not actualize it reliably.
-
The third issue we detected was that very often the message "maximum repetitions reached" in red under the text-message appears. We can't really comprehend why this is happening.
We also determined, that the Android-combination with Meshtastic-devices are "higher-performing" than the IOS-combination. Can you confirm, that this might underlie a constraint of the bluetooth-connection?
The other point is: Are you possibly interested in working on an IOS-App with a branding for our company?
I would be very happy to hear from you. You are also welcome to contact me by e-mail if that seems more convenient to you!
@.*** +43 650 211 56 91 (if you prefer a whatsapp-call)
Have a great day, stay healthy and motivated!
Best regards from mountainous Tyrol/Austria
Lukas Bucher
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Dear Mr. Vander Houwen,
first I have to thank you for your work according to the Meshtastic-App. Great effort from your side!
Let me introduce myself and our company shortly: My name is Lukas Bucher, self employed since 2017. In december 2021 my IT-technician and me founded the company Jellynet GmbH. The company offers - beside optimization of biomass cogeneration plants - disaster protection for municipalities in Austria, Europe. Actually we are working on a failsafe variant of Meshtastic-application coupled with infrastructural transmitters.
My business partner/IT-technician developed an android-version of Jellynet/Meshtastic application with Jellynet-branding. This application works very well.
While some testing scenarios we detected some issues with the IOS-App. Unfortunately we are no specialists in programming IOS-systems, so that is one point why I am writing you.
One problem we detected was, if you go into the channel-chat (not in the single-chat) in messages, then go back to the message-overview, then you jump again in channel-chat, the app freezes/has issues with jumping in the channel-chat again.
Another issue we detected was, that the Meshtastic-device receives messages, but the IOS-App does not actualize it reliably.
The third issue we detected was that very often the message "maximum repetitions reached" in red under the text-message appears. We can't really comprehend why this is happening.
We also determined, that the Android-combination with Meshtastic-devices are "higher-performing" than the IOS-combination. Can you confirm, that this might underlie a constraint of the bluetooth-connection?
The other point is: Are you possibly interested in working on an IOS-App with a branding for our company?
I would be very happy to hear from you. You are also welcome to contact me by e-mail if that seems more convenient to you!
lukas@jellynet.gmbh +43 650 211 56 91 (if you prefer a whatsapp-call)
Have a great day, stay healthy and motivated!
Best regards from mountainous Tyrol/Austria
Lukas Bucher