Keyboard consisting of buttons

[Heidar]

Hello to all!

One of my apps allows users to share messages in a non-supported font and includes an integrated keyboard consisting of 46 buttons. When this keyboard is shown, the device keyboard is hidden. In the beginning, everything worked smoothly, but for a while now the app becomes very slow or even crashes as soon as the integrated keyboard is opened. This is quite annoying for many users as well as for myself. Could it have something to do with the number of buttons? What alternatives are there to a keyboard consisting of buttons?

Many thanks in advance.

[uskiara]

Probably you can find hints and suggestions here ?

HOW TO: Making a custom keyboard with Vanilla App Inventor

SOME NOTES BEFORE I START THIS TUTORIAL I'm not shouting by using Caps, it's just that I'm trying to emphasize stuff. This tutorial has been built up from many solutions here and there. Each old tutorial bits was taken to construct this, and some help from moderators have also been used! You need an extension to create a basic keyboard if you are using a textBox Design the keyboard however you want Set your TextBox to MultiLine for the custom keyboard's Enter / Return key to work. MultiLine …

Best wishes.

[ABG]

@Heidar

but for a while now the app becomes very slow or even crashes as soon as the integrated keyboard is opened.

This sounds more like a code problem.

Canned Reply: ABG- Export & Upload .aia)
Export your .aia file and upload it here.

.
I have not had this problem in my sample app

Wordle In A Day

This week the US news networks have been reporting on a free web game by Josh Wardle called Wordle, similar to Jotto, developed as a personal project and open for all. His variation has: one chance to play per day every one shares the same daily word words have exactly 5 letters you get six guesses You are told which letters match in place (green), which letters match out of place (yellow) which letters don't match anywhere (dark grey). I decided to try to replicate his app in AI2 under t…

[SteveJG]

@Heidar

In the beginning, everything worked smoothly, but for a while now the app becomes very slow or even crashes as soon as the integrated keyboard is opened.

Perhaps this happens because of some feature you added recently. Do you have an aia for an earlier version of the app? If you do, compile it and see if it 'works' better than the existing copy of your app.

I have a keyboard based on a Table of buttons; works real fast.

[Heidar]

Unfortunately, I no longer have an aia of a version that worked perfectly. However, I remember that the problem first occurred either after I had integrated the "Admob Mediation" extension from the developer JEWEL, which I later removed, or after the switch to Android 13. I should add that the app is equipped with numerous extensions, of which I don't know whether they work properly with Android 13. I should also mention that the keyboard buttons are each provided with images, but these have very small file sizes. I have attached a current aia for testing here.
Suetterlin_copy.aia (5.5 MB)

[SteveJG]

@Heidar

the "Admob Mediation" extension from the developer JEWEL, which I later removed

but you added the admobil extension by oseamya I think this free extension is outdated and probably why your app is 's l o w'

Your project Blocks do not load using the main ai server. I expect there are a lot. How many Blocks are in your Project?

[Heidar]

Oseamya's extension works very well and does not cause any problems, not even in my other apps. As already described, the problem only occurs when the „Show Keyboard" button is pressed.

[ABG]

I notice you are not taking advantage of the newer more powerful text replace using dictionary block, for example in this procedure:

Also, you beat up on TinyDB tags '1', '2', '3' a lot.

You might get better performance using local variables for those.

[Heidar]

That is also an important tip. Many thanks for that. No doubt I still make a lot of mistakes. However, that doesn't explain why the app was working without any problems before. Could it perhaps be that since the switch to Android 13, when the keyboard buttons are displayed, all processes associated with these buttons are also called into memory at the same time?