The button will be clicked from another screen. I want to know how will I be able to make “Image A and E” both clickable and so on for the rest of the letters.
Use TinyDB to store, if a button should be clickable or not
Are you aware of tip 1?
Taifun
1 Like
do you think I should just use one screen for this? in the other screen there are 78 Vertical Arrangements, for the activity.
Please explain more what your app is about
How many screens do you have or do you plan to have? Did you copy the screens or do rhey look similar?
Taifun
The purpose of my app is to provide a Filipino Phonetic learning material for young children. There will be sign up, login, 3 levels of activity. there are 21 Filipino phonetic sounds, each consonant will have 5 phonetic sounds, for example , “BA,BE,BI, BO,BU” that is why in Screen (Level 1, there are at least 78 vertical arrangements, 3 levels in total)
What means level of activity and what is their difference?
In the screenshot we can see currently 5 vocals as images and the 21 phonetic sounds for A as inages, ba, ka,, da etc
So after clicking E the images of the phonetic sounds change to be, ke, de, etc?
I did not understand why you need 78 vertical arrangements? That's a lot...
Taifun
Alternatively instead of inages you could use buttons and change the button texts during runtime of the app
Taifun
for ba, there are Ba be bi bo bu,
ba, ka, da , etc,.
ba x 5
ka x 5
the changes fors each level is the type of activity.
first activity, listen and repeat,
second activity listen and match
third activity match each letter to its sounds
after clicking ba there will be ba be bi bo bu
This sounds like a table driven app.
It would probably benefit from consistent sound file names matching with the phonemes.
(Canned Reply: ABG- Export & Upload .aia)
Export your .aia file and upload it here.
FILphla.aia (1.3 MB)
Hello. ABG, thank you for your reply to my concern. Here is the .aia file. Could you please check and, if possible, let me know what I am doing wrong? Thank you!
At first glance at your app
I see a lot of repetition.
Until I can get a sample up for you, i recommend you reading
for a sample of how to reuse components.
You don't need a separate sound or player component for each sound (not that you've uploaded any into your app yet.) Just reuse the same component and change the sound file name as needed just before playing that sound.
And study the list introductions.
Did you need a special font for the text in those images?
Look for ttf files for your special font to allow use of Labels instead.
1 Like
Hello again. I will make sure to read that, thank you.
Yes, a lot of repetition indeed. I also used a lot of vertical and horizontal arrangements because I find it complicated to position everything, do you think that is a wise move? or will it end with an error in the future?
Not at all, I don't need a special font for the text in those images.
Thank you.
Nesting Horizontal and Vertical Arrangements is fine, as long as you really need to show everything simultaneously, like a chart.
They make a fine scaffolding.
I have yet to see if you are doing visibility juggling versus data juggling.
I tried to redo the Login, signup, and first screen. I put everything in one screen. What do you think about the FilipoPhoneticScreen, the one with a lot of letter images. Do you think I should changed them to buttons instead of images? Thank you. I have to finish this by the end of September.
I can no longer load this app on the code server, where I work on user apps.
Something about the app is too big.
I made some changes and deleted some screens. Would you mind trying again? I also changed the images and replaced them with buttons.
FILphla (1).aia (1.3 MB)
I will try to decrease the vertical arrangements and probably remove one level.
Where are your sounds?
I haven't put the sounds yet, I will be recording them this weekend.
21 * 5 = 105 sound files?
Start with ba ... du (3 consonants, 5 vowels, all combos) to allow engine testing