Hello Adalo Community,
I recently launched my app on the App Store and Google Play, but I’ve found that it’s running quite slow. The app has 157 screens, 50 data collections, and approximately 9,000 records. Given the performance issues, I am exploring ways to improve the app’s speed and efficiency.
I’ve been considering migrating my backend to Xano to leverage its robust and scalable features. However, I’m uncertain about the best approach. Is it possible to migrate the existing app’s data and backend operations to Xano while still using the current Adalo front end? Or would it be more effective to start fresh with a new setup?
Additionally, I’m contemplating whether switching to FlutterFlow might be a better solution for long-term performance and scalability. Is there any alternative to Xano that might be more suitable for my needs, or is Xano the best option for enhancing my app’s performance?
I would appreciate any advice or experiences from the community regarding these potential paths. What do you think would be the most efficient and effective solution to improve my app’s performance?
Thank you for your help!
Best regards,
2 Likes
Hey there. Sorry you’re experiencing issues here. Can you link me to your app on the App Store and Google Play and tell me which parts seem slow? I’d like to share it with my eng team. Thanks!
1 Like
The primary areas where we’re experiencing significant slowdowns include navigation between screens, data fetching, and loading times for lists and collections. Essentially, the overall responsiveness of the app is not meeting our expectations.
We’ve invested a substantial amount of time and money into developing this app, and we’ve been working with Adalo since 2021. We are really passionate about this project, and it’s disheartening to see our dream facing these hurdles.
We are late for our official launch, and the current performance issues are causing us a lot of concern. We don’t want to lose our dream because of these technical challenges. We urgently need a solution to improve the app’s performance.
Please share this with your engineering team and help us find a way to resolve these issues. We’re eager to make this work and bring our vision to life with Adalo.
Thank you so much for your support.
I’ve shared this with my head of engineering. Thanks for passing it along. This is a beautiful app and I can tell you’ve put a ton of work into it.
1 Like
Thanks to you sharing the app with us we’ve identified a few issues with images that might be slowing down your app. I’ve got an engineer working on an improvement there. I’ll post here when it goes out.
Update: these updates have gone out
Thank you so much for your response and efforts to improve our app’s performance. We deeply appreciate it. However, we urgently need further assistance as we are losing both money and time. We are exploring Xano but finding it challenging, especially since there are no comprehensive resources for using it with Adalo projects. As mechanical engineers, Adalo gave us hope and the ability to pursue our dream of creating this app. We trust and love Adalo and believe it can help us succeed. Please guide us through this.
Thank you so much for your kind words! We’re thrilled to hear that you like the design. It’s feedback like yours that keeps us motivated and inspired. We’re working hard to make our app the best it can be, and your support means a lot to us. If you have any suggestions or feedback, we’d love to hear it!
1 Like
Migrating to Xano on an existing app is pretty tricky. It’s definitely easiest to use Xano if you used it on day one of your app build. If you want to migrate from Adalo collections to Xano, I’d recommend working with an expert who has Xano experience. If you want to do it yourself, check out Xano’s video on this topic. https://www.youtube.com/watch?v=F1dVHpCxigE
1 Like
Thanks for your assistance so far. However, I need answers to the following questions to further diagnose the issues we’re facing:
- How many CPUs are assigned to our product?
- What type of disks is provided for storage - SSD or HDD?
- Are there logs available on this platform to help us understand why we have high response times?
- We have tried using Xano as the backend server and have created all API calls on it, but we are still experiencing slowness. Can you help identify the cause of this issue?
- What is the amount of memory allocated for this app?
Your help in addressing these questions will be greatly appreciated.
1 Like
I think this is a very important issue and deciding for me whether i would stick to adalo yes or no. Curious how this unfolds.
I recently received a report from Apple while trying to publish my app, and I’m experiencing significant performance issues and HTTP 500 errors. I’m not a coder, so I’m reaching out for help to understand and resolve these problems. Here’s a detailed breakdown of the issues and what I’ve done so far.
Issues Reported by Apple
-
Unmet Peer Dependencies and Deprecated Packages:
- The report mentions several warnings about unmet peer dependencies for various packages such as
react, react-native, and react-dom.
- There are deprecated packages and APIs being used, which might contribute to performance issues.
-
Memory Leaks and Performance Warnings:
- Warnings about modules like
inflight used by glob leaking memory, which can severely impact app performance.
-
Incorrect Peer Dependencies:
- Libraries like
react-native-webview and react-datepicker have incorrect peer dependencies specified, leading to potential compatibility issues and unexpected behavior.
-
Usage of Unsupported Modules:
- Warnings about the usage of unsupported modules like
rimraf and suggestions to use alternatives indicate that there might be better, more performant libraries available for my needs.
Steps I’ve Taken So Far
-
Updated and Optimized Components:
- Ensured that all components used in the app are up to date and optimized.
- Example: Updated form components and removed unnecessary fields to streamline the app.
-
Reduced the Number of Screens:
- Consolidated similar screens to reduce the overall number.
- Example: Merged multiple user profile screens into a single screen with conditional visibility.
-
Optimized Images and Media:
- Compressed images and ensured videos are in a suitable format and resolution.
- Example: Used TinyPNG to compress images before uploading them to Adalo.
-
Simplified Navigation:
- Streamlined the navigation structure for better performance.
- Example: Implemented a tab bar for navigation instead of nested menus.
What I Need Help With
-
Investigating Server Errors (HTTP 500 Errors):
- Need assistance in understanding and fixing the HTTP 500 errors.
- Example: Providing specific instances of HTTP 500 errors to Adalo support for detailed investigation.
-
Upgrading Plan and Resources:
- Would upgrading my plan provide more resources (CPU, memory, etc.) to improve performance?
- Example: Discussing with Adalo support the potential benefits of upgrading to a higher-tier plan.
-
Performance Optimization Assistance:
- Any additional advice or tools for optimizing my app’s performance would be greatly appreciated.
- Example: Reviewing my app setup with Adalo support and getting specific recommendations for improvements.
-
Debugging and Error Logs:
- Help in interpreting the error logs and resolving the issues causing these errors.
- Example: Sharing the error logs with Adalo support and asking for a detailed explanation and resolution steps.
Example of Issues
- HTTP 500 Errors: Encountered while trying to perform certain actions within the app.
- Slow Performance: Noticed particularly during screen transitions and data load.
Request for Assistance
I’m looking for detailed guidance on what steps to take next. As a non-coder, I would appreciate clear, step-by-step instructions on how to address these issues within the Adalo platform and what might require intervention from Adalo support.
Thank you for your support!
Is Apple rejecting your app based on those items? Several of the items listed relate to utilities that are used simply to run a build of your app and do not affect runtime in any way (Glob, Inflight, rimraf, etc.)
For your other question, we don’t currently offer any additional performance-based upgrades. To date, performance improvements and updates go out to all customers and apps.
I do want to make it clear again that I have my engineers studying your app specifically to see what we can learn and if there are any improvements we can make. They have already identified and launched one such improvement and are on the case to see what else we can do.
3 Likes
Hi Josh,
Thank you so much for your prompt and thorough response. I genuinely appreciate the attention and effort your team is putting into investigating and improving the performance of our app.
To clarify, Apple did not reject the app based on the items listed in their report. However, I wanted to share the log file they provided to assist your team in identifying any potential issues. We believe that collaborating closely can help us pinpoint and resolve the root causes of the performance challenges we’re experiencing.
We have immense trust and faith in your team’s expertise and capabilities. We are confident that with your ongoing efforts, we’ll see significant improvements. On our end, we’re also doing everything we can to optimize and identify any contributing factors. We see our success as intertwined with yours—your achievements directly impact our success, and we are committed to working together to reach our shared goals.
Thank you again for your dedication and support. We look forward to any further guidance or recommendations you can provide to help us improve our app’s performance.
So far by analyzing your app, we’ve identified some issues with image loading and the Lottie component. We’ve pushed out performance improvements for both of these issues. I’m not sure if it’ll have a dramatic impact on your app but it’s worth running another build just to make sure you have these improvements. We’re continuing to dig for more root causes today as well. Thanks.
1 Like
Hi Josh,
Thank you so much for your continued support and efforts in analyzing and improving our app. We really appreciate the performance improvements related to image loading and the Lottie component that you’ve already pushed out.
We will run another build to incorporate these improvements and observe the impact on the app’s performance. We are optimistic that these changes will make a positive difference.
Your team’s dedication to identifying and addressing the root causes of the performance issues means a lot to us. We have full confidence in your ability to help us resolve these issues. Please let us know if there’s any additional information or testing we can assist with on our end to further support your efforts.
Thanks again for your hard work and commitment. Our success is intertwined with yours, and we are grateful for the collaboration.
Hi Josh,
Thank you for your continuous support and the improvements you’ve already made. We’ve taken your advice and have migrated all our data and over 70% of our functions to Xano. This has noticeably improved the data fetching speed, and the app’s performance is better than before. However, we’re still experiencing significant slowness in the app, especially in navigating through screens and overall responsiveness.
Here’s a detailed summary of what we’ve done:
-
Database Migration:
- We’ve moved all data from Adalo’s internal collections to Xano. This includes user data, reviews, places, and activities. The data fetching from Xano is significantly faster.
-
Optimizations Implemented:
- Image Optimization: Resized and compressed images before uploading them to Adalo.
- Lazy Loading: Implemented lazy loading for images and data.
- Simplified Layouts: Reduced the number of nested components and simplified screen designs.
- Efficient Data Handling: Implemented pagination and optimized data fetching logic.
-
Current Issues:
- Despite these optimizations, the app still experiences lag, especially in screen transitions and UI responsiveness.
- The frontend seems to be the bottleneck now, even though data operations have improved.
We’ve noticed that the time between tap and UI change is still in the order of seconds, and media assets take time to fully appear on the screen. This indicates that the issue might lie within the frontend rendering and the complexity of components being used.
We’ve done everything we could from our end and would greatly appreciate further guidance or insights from your team. Specifically, if there are any additional optimizations or configurations within Adalo that we might have missed, or if there’s a possibility of having more granular control over the frontend performance aspects.
Thank you again for your help. We believe in the potential of Adalo and are committed to making our app a success with your support.
1 Like
We can see this in your app too and we’re trying to track it down. You might try turning off screen transition animations, which can help things feel a bit snappier. Otherwise, I’ll let you know if my team finds any other improvements here.
1 Like