I'm curious how other developers approach the planning stage of a new mobile app. Before writing the first line of code, I usually try to understand the core requirements, target devices, technical limitations, and which features actually need to be included in the first version. I'm also interested in how larger teams approach this. When several developers are involved in a project, does a mobile app development company]usually define the architecture and technology stack completely before development starts, or do you leave some of those decisions open as the project evolves? How much planning do you normally do before starting development? Have you found that spending more time on planning actually prevents problems later, or can too much upfront planning slow the project down?I'm curious how other developers approach the planning stage of a new mobile app. Before writing the first line of code, I usually try to understand the core requirements, target devices, technical limitations, and which features actually need to be included in the first version. I'm also interested in how larger teams approach this. When several developers are involved in a project, does a mobile app development company usually define the architecture and technology stack completely before development starts, or do you leave some of those decisions open as the project evolves? How much planning do you normally do before starting development? Have you found that spending more time on planning actually prevents problems later, or can too much upfront planning slow the project down?

Check out my LinkedIn Profile for: Project history and work experience Informative posts and articles about Qt and QML Ways that I could help you and your team!

Hi, I think the wiki has the starting point Hope it helps

@Emma-2000 said in Squish for Java, select an item in a list box: I’ve run into a similar issue with long JavaFX lists where the target item isn’t initially visible. Using the component’s available items/model instead of relying only on scrolling seems much more reliable, especially when the test input changes dynamically. Agreed on using the model and toolkit API to access or even scroll a particular object into view. (Squish for Java tries to automatically scroll an object into view upon mouseClick(). And one can pass Button.NoButton (https://doc.qt.io/squish/java-convenience-api.html#java-convenience-function-parameters) to mouseClick() to trigger the scrolling attempt without performing a mouse click.) The approach with obj.items.length, obj.items.get(i) and assigning obj.value looks particularly useful for making the test independent of the item’s position in the list. obj.items.get(i) requires specifying the index of the item, which I intuitively understand to be the "position in the list". Perhaps by "position" you meant the location on the screen? If so, yes, hardcoded positions are better to be avoided. (Squish is using screen positions for sending events, etc. - but it determines/calculates these screen locations at runtime.) Ah, after further consideration, you probably meant iterating over the items until the desired one is found. Alright.

Nice..now he knew whether to perform certification

Qt for HarmonyOS development with 6.12.0 https://wiki.qt.io/Qt_for_HarmonyOS_development_with_6.12.0 https://lists.qt-project.org/pipermail/development/2026-August/047432.html #Qt #HarmonyOS #OpenHarmony #Huawei

[image: acc63b82-54bc-40d4-a5d1-005d45c1cd23.png]

Ok, akismet triggering is not always clear. Beside this issue, what was your question about ?