Wasting my precious credit
I am developing a web app for my job as a Customer Representative, something relatively simple where I collect data from Discord via bot integration and extract insights like ticket duration, which agent handled the ticket, etc. In the beginning, everything was working very well; conversations with the AI were productive, it solved issues, and identified errors. However, over time, I started noticing that it began spending credits pointlessly, for example, asking me two or three times if it could do something I had already asked it to do. Something like this: User: Do X, Y, and Z. Base44: Okay, I will do X, Y, and Z, and to do this, I need to modify such-and-such file. User: Okay. Base44: All right, I will proceed and implement X, Y, and Z. Can I continue? Man, do you understand that when you are charged per interaction and the AI does this, it’s just stealing your credits? Another thing that has been bothering me A LOT is regarding solutions that don't solve anything. I bring up the problem, explain what is happening, and after a few minutes and credits spent, it says it's resolved, but it’s not. A simple check of the UI is enough to see that it’s exactly the same. Sometimes I have to insist 3 or 4 times before it finally finds the bug and fixes it. Along these same lines, it has been applying manual fixes; instead of solving the problem, it creates a workaround that only fixes that specific point, but the system is meant to be automatic, which means that in the next update sync, the error will persist for new cases. I’ve already asked it not to do this, to indicate what is happening so I can check. Sometimes the bot lost a permission and the AI doesn't have the data, I don't know, it’s there for that: to show me the error. But even when I explicitly ask it not to work with manual workarounds, in the very next message, it simply applies a manual workaround. It’s completely crazy. I am happy with the result the app is becoming, but I’m spending credits to correct what the AI should have noticed. It seems absurd to me for it to send "Done, I fixed it," and in the next message, after I say it’s not fixed, it says "You are correct, I am unable to do X, Y, and Z." Why didn't you tell me before that you couldn't do it? It feels like when the problems start getting complex, it just "fakes it" and pretends it’s solving it, but it isn’t. Taking into account that credits do not accumulate and they are expensive, the use of credits MUST be VERY precise. The AI has to perform every verification before saying that a problem is resolved.
Matheus Manholer About 6 hours ago
Feature Request
Wasting my precious credit
I am developing a web app for my job as a Customer Representative, something relatively simple where I collect data from Discord via bot integration and extract insights like ticket duration, which agent handled the ticket, etc. In the beginning, everything was working very well; conversations with the AI were productive, it solved issues, and identified errors. However, over time, I started noticing that it began spending credits pointlessly, for example, asking me two or three times if it could do something I had already asked it to do. Something like this: User: Do X, Y, and Z. Base44: Okay, I will do X, Y, and Z, and to do this, I need to modify such-and-such file. User: Okay. Base44: All right, I will proceed and implement X, Y, and Z. Can I continue? Man, do you understand that when you are charged per interaction and the AI does this, it’s just stealing your credits? Another thing that has been bothering me A LOT is regarding solutions that don't solve anything. I bring up the problem, explain what is happening, and after a few minutes and credits spent, it says it's resolved, but it’s not. A simple check of the UI is enough to see that it’s exactly the same. Sometimes I have to insist 3 or 4 times before it finally finds the bug and fixes it. Along these same lines, it has been applying manual fixes; instead of solving the problem, it creates a workaround that only fixes that specific point, but the system is meant to be automatic, which means that in the next update sync, the error will persist for new cases. I’ve already asked it not to do this, to indicate what is happening so I can check. Sometimes the bot lost a permission and the AI doesn't have the data, I don't know, it’s there for that: to show me the error. But even when I explicitly ask it not to work with manual workarounds, in the very next message, it simply applies a manual workaround. It’s completely crazy. I am happy with the result the app is becoming, but I’m spending credits to correct what the AI should have noticed. It seems absurd to me for it to send "Done, I fixed it," and in the next message, after I say it’s not fixed, it says "You are correct, I am unable to do X, Y, and Z." Why didn't you tell me before that you couldn't do it? It feels like when the problems start getting complex, it just "fakes it" and pretends it’s solving it, but it isn’t. Taking into account that credits do not accumulate and they are expensive, the use of credits MUST be VERY precise. The AI has to perform every verification before saying that a problem is resolved.
Matheus Manholer About 6 hours ago
Feature Request
Atualização de Multiplos Apps
Se temos a opção de criar cópias de apps, deveriamos ter a opção de atualizar esses apps filhos ou não de maneira escalável evitando erros e retrabalhos.
Dora West About 7 hours ago
Feature Request
Atualização de Multiplos Apps
Se temos a opção de criar cópias de apps, deveriamos ter a opção de atualizar esses apps filhos ou não de maneira escalável evitando erros e retrabalhos.
Dora West About 7 hours ago
Feature Request
generate image different formats and upscaling
It would be amazing if you could tell the generate image AI to create images in various formats (e.g. 4:5) and also upscale pixel (e.g. for print on demand API that usually need 300 DPI with e.g. 4800×4800 pixel) Currently the generate image functionality can only create images in 1:1 format in 1024×1024
Luiz Zuch About 13 hours ago
Feature Request
generate image different formats and upscaling
It would be amazing if you could tell the generate image AI to create images in various formats (e.g. 4:5) and also upscale pixel (e.g. for print on demand API that usually need 300 DPI with e.g. 4800×4800 pixel) Currently the generate image functionality can only create images in 1:1 format in 1024×1024
Luiz Zuch About 13 hours ago
Feature Request
Feature Request: dropped_fields in update() response
When calling entity.update(), fields with field-level rls.read restrictions are silently dropped. The response returns modified_count: 1, suggesting success — but the fields are never persisted. Antworten Suggestion: Add a dropped_fields array to the update response (e.g. "dropped_fields": ["phone", "birth_year"]) so developers immediately know which fields were filtered out. Antworten This would have saved us several hours of debugging. The silent drop + success response is very misleading, especially when using asServiceRole where you'd expect full write access.
akrumes@outlook.com About 14 hours ago
Feature Request
Feature Request: dropped_fields in update() response
When calling entity.update(), fields with field-level rls.read restrictions are silently dropped. The response returns modified_count: 1, suggesting success — but the fields are never persisted. Antworten Suggestion: Add a dropped_fields array to the update response (e.g. "dropped_fields": ["phone", "birth_year"]) so developers immediately know which fields were filtered out. Antworten This would have saved us several hours of debugging. The silent drop + success response is very misleading, especially when using asServiceRole where you'd expect full write access.
akrumes@outlook.com About 14 hours ago
Feature Request
Need better scalability options for high-volume production apps
We are building a production app on Base44 and overall we really like the platform, but we are starting to hit scalability limits that are becoming a real blocker. We understand and appreciate the reason for guardrails such as rate limits and bulk fetch caps. They protect app performance and prevent misuse. The issue is that for apps with real user growth, these limits can also become a bottleneck even after doing substantial optimization work. In our case, we already: consolidated multiple frontend requests into backend data fetchers added pagination in the main heavy screens reduced redundant reads and invalidations cached global counters/stats simplified several expensive screens and query flows made some counts approximate where exact values were too expensive Even after all of that, we still run into problems such as: 429 Rate limit exceeded during burst traffic lead/webhook ingestion affecting the rest of the app difficulty scaling admin/importer dashboards as usage grows architectural tradeoffs where we have to choose between correctness and staying within platform limits A few areas where more flexibility would help a lot: Higher rate limit tiers for production apps Especially for apps with real traffic, background processing, and webhook ingestion. Better support for webhook/high-ingestion workloads If one burst of incoming webhooks can trigger throttling for the whole app, that becomes a major risk. More scalable backend querying patterns The current bulk-fetch ceiling is understandable, but we would benefit from stronger server-side aggregation, counting, and pagination primitives so we do not have to choose between expensive scans and incomplete data. App-level scalability plans or add-ons It would be great to have a way to move a serious app into a higher-capacity plan with clearer operational guarantees. Better isolation between workloads For example, preventing one noisy flow like lead intake from degrading the rest of the app. We are not asking for unsafe defaults. We are asking for a path for serious apps to grow on Base44 without hitting hard ceilings too early. We would love to see: higher-capacity plans optional higher rate limits stronger server-side data tools better ingestion/webhook handling more explicit support for high-growth production apps Base44 is excellent for building quickly, and we would really like to keep growing on it. A clearer scalability path would make a huge difference.
Admin Team About 16 hours ago
Feature Request
Need better scalability options for high-volume production apps
We are building a production app on Base44 and overall we really like the platform, but we are starting to hit scalability limits that are becoming a real blocker. We understand and appreciate the reason for guardrails such as rate limits and bulk fetch caps. They protect app performance and prevent misuse. The issue is that for apps with real user growth, these limits can also become a bottleneck even after doing substantial optimization work. In our case, we already: consolidated multiple frontend requests into backend data fetchers added pagination in the main heavy screens reduced redundant reads and invalidations cached global counters/stats simplified several expensive screens and query flows made some counts approximate where exact values were too expensive Even after all of that, we still run into problems such as: 429 Rate limit exceeded during burst traffic lead/webhook ingestion affecting the rest of the app difficulty scaling admin/importer dashboards as usage grows architectural tradeoffs where we have to choose between correctness and staying within platform limits A few areas where more flexibility would help a lot: Higher rate limit tiers for production apps Especially for apps with real traffic, background processing, and webhook ingestion. Better support for webhook/high-ingestion workloads If one burst of incoming webhooks can trigger throttling for the whole app, that becomes a major risk. More scalable backend querying patterns The current bulk-fetch ceiling is understandable, but we would benefit from stronger server-side aggregation, counting, and pagination primitives so we do not have to choose between expensive scans and incomplete data. App-level scalability plans or add-ons It would be great to have a way to move a serious app into a higher-capacity plan with clearer operational guarantees. Better isolation between workloads For example, preventing one noisy flow like lead intake from degrading the rest of the app. We are not asking for unsafe defaults. We are asking for a path for serious apps to grow on Base44 without hitting hard ceilings too early. We would love to see: higher-capacity plans optional higher rate limits stronger server-side data tools better ingestion/webhook handling more explicit support for high-growth production apps Base44 is excellent for building quickly, and we would really like to keep growing on it. A clearer scalability path would make a huge difference.
Admin Team About 16 hours ago
Feature Request
White label requests + customizations
The login UI is managed by Base44's platform and can't be fully white-labeled at this time and this would be a preferred feature. Custom domain auth / white-label login pages as well. Custom SMS sender name is also not currently a configurable feature in Base44 and should be. Essentially everything should have an option to be white labeled, especially for a paying annual customer like myself. Thank you for considering! :)
Kimberly Blair About 16 hours ago
Feature Request
White label requests + customizations
The login UI is managed by Base44's platform and can't be fully white-labeled at this time and this would be a preferred feature. Custom domain auth / white-label login pages as well. Custom SMS sender name is also not currently a configurable feature in Base44 and should be. Essentially everything should have an option to be white labeled, especially for a paying annual customer like myself. Thank you for considering! :)
Kimberly Blair About 16 hours ago
Feature Request
Porfavor permitir las fnciones Backend en el plan más barato
LLevo tiempo construyendo con vosotros y ahora que no necesito desarrollar tanto me gustaria que las funciones backend funcionen con el plan más barato e incluso el gratuito, Por favor os invito a que considereis este cambio
Oriol Garcia About 17 hours ago
Feature Request
Porfavor permitir las fnciones Backend en el plan más barato
LLevo tiempo construyendo con vosotros y ahora que no necesito desarrollar tanto me gustaria que las funciones backend funcionen con el plan más barato e incluso el gratuito, Por favor os invito a que considereis este cambio
Oriol Garcia About 17 hours ago
Feature Request
push notification and deep links for custom domains
i think those are integral additions for base 44. very basic features for ios apps
YOAV buskila About 18 hours ago
Feature Request
push notification and deep links for custom domains
i think those are integral additions for base 44. very basic features for ios apps
YOAV buskila About 18 hours ago
Feature Request
SSR Request
Hi Base44 team, I'm running a business website on Base44 and have invested heavily in SEO — custom page titles, meta descriptions, Open Graph tags, canonical URLs, and structured JSON-LD data — all configured per route. Because Base44 apps are client-side rendered, these tags are injected by JavaScript after page load. This means: Social sharing scrapers (Facebook, Instagram, iMessage, etc.) don't wait for JS and pull blank or default previews SEO crawlers may not consistently read dynamically-set tags across all routes I'd love to see Base44 support pre-rendering or server-side rendering (SSR) — where each route's HTML is served with the correct , , and Open Graph tags already present in the raw response. Even static pre-rendering (generating HTML snapshots per route at deploy time) would solve the majority of this. This would make Base44 significantly more viable for public-facing business websites that depend on discoverability. Happy to share my current SEO setup as a reference use case. Thanks
Krystal Brook About 21 hours ago
Feature Request
SSR Request
Hi Base44 team, I'm running a business website on Base44 and have invested heavily in SEO — custom page titles, meta descriptions, Open Graph tags, canonical URLs, and structured JSON-LD data — all configured per route. Because Base44 apps are client-side rendered, these tags are injected by JavaScript after page load. This means: Social sharing scrapers (Facebook, Instagram, iMessage, etc.) don't wait for JS and pull blank or default previews SEO crawlers may not consistently read dynamically-set tags across all routes I'd love to see Base44 support pre-rendering or server-side rendering (SSR) — where each route's HTML is served with the correct , , and Open Graph tags already present in the raw response. Even static pre-rendering (generating HTML snapshots per route at deploy time) would solve the majority of this. This would make Base44 significantly more viable for public-facing business websites that depend on discoverability. Happy to share my current SEO setup as a reference use case. Thanks
Krystal Brook About 21 hours ago
Feature Request
Multilingual login and sign-up page
The login and sign-up page is entirely in English and cannot be customized. For apps targeting non-English speaking markets (like France), this creates a major friction point for users who don't speak English. I lost a client because of this. Please add multilingual support or allow app owners to customize the language of the login/sign-up page to match the language of their app
Matheo14 About 21 hours ago
Feature Request
Multilingual login and sign-up page
The login and sign-up page is entirely in English and cannot be customized. For apps targeting non-English speaking markets (like France), this creates a major friction point for users who don't speak English. I lost a client because of this. Please add multilingual support or allow app owners to customize the language of the login/sign-up page to match the language of their app
Matheo14 About 21 hours ago
Feature Request
Feature Request: Localization of Authentication Pages and System Emails
Hello Base44 team, I’d like to request support for translating and customizing authentication-related content. Currently, it’s not possible to change the language or text for: authentication pages (login, signup, password reset) system emails (verification, welcome, password reset) This is a critical feature for non-English projects and international products. The ability to fully localize these elements would significantly improve user experience and conversion. Please consider adding: multi-language support for auth pages editable email templates for all system messages Thank you!
Leonardo Macedonski 1 day ago
Feature Request
Feature Request: Localization of Authentication Pages and System Emails
Hello Base44 team, I’d like to request support for translating and customizing authentication-related content. Currently, it’s not possible to change the language or text for: authentication pages (login, signup, password reset) system emails (verification, welcome, password reset) This is a critical feature for non-English projects and international products. The ability to fully localize these elements would significantly improve user experience and conversion. Please consider adding: multi-language support for auth pages editable email templates for all system messages Thank you!
Leonardo Macedonski 1 day ago
Feature Request
Android TV app upload support
Hi, has anyone been working on editing LEANBACK_LAUNCHER (Leanback feature, no touchscreen requirement) as Base44's mobile app wrapper is designed for standard Android phones/tablets, and not Android TV? I need to publish my app to use it on TV and have no programming knowledge to make these changes. Any one may help?
Maximiliano Rojo 1 day ago
Feature Request
Android TV app upload support
Hi, has anyone been working on editing LEANBACK_LAUNCHER (Leanback feature, no touchscreen requirement) as Base44's mobile app wrapper is designed for standard Android phones/tablets, and not Android TV? I need to publish my app to use it on TV and have no programming knowledge to make these changes. Any one may help?
Maximiliano Rojo 1 day ago
Feature Request
I would need we can connect to Google Maps
I am building share riding app and would love if we can connect to Google map and Google Place
Askar DG KAMIS (IDHotelier) 1 day ago
🔌 Integrations
I would need we can connect to Google Maps
I am building share riding app and would love if we can connect to Google map and Google Place
Askar DG KAMIS (IDHotelier) 1 day ago
🔌 Integrations
Add a reference abilities
When I want to build a game or app similar to another, I want this builder to be able to pull refewrences from the internet to use as a guide for what im looking for
merry jane 1 day ago
🔌 Integrations
Add a reference abilities
When I want to build a game or app similar to another, I want this builder to be able to pull refewrences from the internet to use as a guide for what im looking for
merry jane 1 day ago
🔌 Integrations
Apple In-App Purchase (StoreKit) Support for iOS I am building an app using Base44 and submitting it to the Apple App Store. The app includes paid digital features and subscriptions. Currently, Base44 does not support Apple’s StoreKit / In-App Purchase system, which is required by Apple’s App Store guidelines (3.1.1) for any digital goods or subscriptions offered within the app. Because of this limitation, I am unable to: - Offer subscriptions inside the iOS app - Display pricing or upgrade options in a compliant way - Monetize iOS users properly This forces me to remove all pricing and payment flows from the iOS version of the app, which significantly impacts the user experience and business model. Requested features: - Native support for Apple In-App Purchase (auto-renewable subscriptions) - Ability to configure Apple product IDs within Base44 - Purchase handling (subscribe, restore purchases) - Receipt validation and subscription status tracking - Platform-specific logic (iOS vs web) This feature is critical for any app that intends to monetize on iOS. Please provide an estimated timeline if possible.
Feature Request: Apple In-App Purchase (StoreKit) Support for iOS I am building an app using Base44 and submitting it to the Apple App Store. The app includes paid digital features and subscriptions. Currently, Base44 does not support Apple’s StoreKit / In-App Purchase system, which is required by Apple’s App Store guidelines (3.1.1) for any digital goods or subscriptions offered within the app. Because of this limitation, I am unable to: Offer subscriptions inside the iOS app Display pricing or upgrade options in a compliant way Monetize iOS users properly This forces me to remove all pricing and payment flows from the iOS version of the app, which significantly impacts the user experience and business model. Requested features: Native support for Apple In-App Purchase (auto-renewable subscriptions) Ability to configure Apple product IDs within Base44 Purchase handling (subscribe, restore purchases) Receipt validation and subscription status tracking Platform-specific logic (iOS vs web) This feature is critical for any app that intends to monetize on iOS. Please provide an estimated timeline if possible. “Are there any beta features or workarounds for StoreKit integration?” Sometimes platforms have: Hidden beta features Private integrations
cuetonobc@aol.com 1 day ago
Feature Request
Apple In-App Purchase (StoreKit) Support for iOS I am building an app using Base44 and submitting it to the Apple App Store. The app includes paid digital features and subscriptions. Currently, Base44 does not support Apple’s StoreKit / In-App Purchase system, which is required by Apple’s App Store guidelines (3.1.1) for any digital goods or subscriptions offered within the app. Because of this limitation, I am unable to: - Offer subscriptions inside the iOS app - Display pricing or upgrade options in a compliant way - Monetize iOS users properly This forces me to remove all pricing and payment flows from the iOS version of the app, which significantly impacts the user experience and business model. Requested features: - Native support for Apple In-App Purchase (auto-renewable subscriptions) - Ability to configure Apple product IDs within Base44 - Purchase handling (subscribe, restore purchases) - Receipt validation and subscription status tracking - Platform-specific logic (iOS vs web) This feature is critical for any app that intends to monetize on iOS. Please provide an estimated timeline if possible.
Feature Request: Apple In-App Purchase (StoreKit) Support for iOS I am building an app using Base44 and submitting it to the Apple App Store. The app includes paid digital features and subscriptions. Currently, Base44 does not support Apple’s StoreKit / In-App Purchase system, which is required by Apple’s App Store guidelines (3.1.1) for any digital goods or subscriptions offered within the app. Because of this limitation, I am unable to: Offer subscriptions inside the iOS app Display pricing or upgrade options in a compliant way Monetize iOS users properly This forces me to remove all pricing and payment flows from the iOS version of the app, which significantly impacts the user experience and business model. Requested features: Native support for Apple In-App Purchase (auto-renewable subscriptions) Ability to configure Apple product IDs within Base44 Purchase handling (subscribe, restore purchases) Receipt validation and subscription status tracking Platform-specific logic (iOS vs web) This feature is critical for any app that intends to monetize on iOS. Please provide an estimated timeline if possible. “Are there any beta features or workarounds for StoreKit integration?” Sometimes platforms have: Hidden beta features Private integrations
cuetonobc@aol.com 1 day ago
Feature Request
Intergating store kit and revenue cat for iOS submission.
apple storekit since base44 currently wraps apps as web views, there’s no way for me to use storekit right now do you have an estimated timeline for when native storekit support will be available in the ios build pipeline? this is the main blocker preventing me from launching and monetizing my app also, are there any recommended workarounds you suggest in the meantime that will pass apple review? thanks if you want to push a little harder (which you should), add this at the end: if there is no short term solution, should i move off base44 for ios if i want to support subscriptions?
Cullen Daniel’s 1 day ago
Feature Request
Intergating store kit and revenue cat for iOS submission.
apple storekit since base44 currently wraps apps as web views, there’s no way for me to use storekit right now do you have an estimated timeline for when native storekit support will be available in the ios build pipeline? this is the main blocker preventing me from launching and monetizing my app also, are there any recommended workarounds you suggest in the meantime that will pass apple review? thanks if you want to push a little harder (which you should), add this at the end: if there is no short term solution, should i move off base44 for ios if i want to support subscriptions?
Cullen Daniel’s 1 day ago
Feature Request
Incorporar opción para monetizar en google play y apple play
Incorporar sistema de pagos (StoreKit / Google Play Billing) para contenido digital (suscripciones in-app, funciones premium, etc.). URGENTE
Psicología Clínica 1 day ago
Feature Request
Incorporar opción para monetizar en google play y apple play
Incorporar sistema de pagos (StoreKit / Google Play Billing) para contenido digital (suscripciones in-app, funciones premium, etc.). URGENTE
Psicología Clínica 1 day ago
Feature Request
Feature Request – Add-On Purchase for Message / Integration Credits
I would like to suggest a feature that would greatly improve flexibility for users. It would be very helpful to have an option to purchase additional message credits or integration credits without upgrading the entire plan. This would allow users to continue on their existing plan and simply top up credits whenever needed. Currently, upgrading the plan is the only way to increase limits, which may not always be necessary for users who only need occasional extra usage. Adding a pay-as-you-go or top-up system for credits would make the platform more flexible and cost-effective.
Naresh G 1 day ago
Feature Request
Feature Request – Add-On Purchase for Message / Integration Credits
I would like to suggest a feature that would greatly improve flexibility for users. It would be very helpful to have an option to purchase additional message credits or integration credits without upgrading the entire plan. This would allow users to continue on their existing plan and simply top up credits whenever needed. Currently, upgrading the plan is the only way to increase limits, which may not always be necessary for users who only need occasional extra usage. Adding a pay-as-you-go or top-up system for credits would make the platform more flexible and cost-effective.
Naresh G 1 day ago
Feature Request
AI IS NOT REVERTING OR I CANT RESTOE ANYTING AFTER ANY SYNTHAX ERROR FIXED , MY WHOLE SYSTEM IS FUCKED. EVERY TIME i SEE THERE IS SOMETHING MISSING AFTER SYNTHEX ERRO FIXED AND UNABLE TO RESTORE OR REVERT
AI IS NOT REVERTING OR I CANT RESTOE ANYTING AFTER ANY SYNTHAX ERROR FIXED , MY WHOLE SYSTEM IS FUCKED. EVERY TIME i SEE THERE IS SOMETHING MISSING AFTER SYNTHEX ERRO FIXED AND UNABLE TO RESTORE OR REVERT
Ordering Website 1 day ago
Feature Request
AI IS NOT REVERTING OR I CANT RESTOE ANYTING AFTER ANY SYNTHAX ERROR FIXED , MY WHOLE SYSTEM IS FUCKED. EVERY TIME i SEE THERE IS SOMETHING MISSING AFTER SYNTHEX ERRO FIXED AND UNABLE TO RESTORE OR REVERT
AI IS NOT REVERTING OR I CANT RESTOE ANYTING AFTER ANY SYNTHAX ERROR FIXED , MY WHOLE SYSTEM IS FUCKED. EVERY TIME i SEE THERE IS SOMETHING MISSING AFTER SYNTHEX ERRO FIXED AND UNABLE TO RESTORE OR REVERT
Ordering Website 1 day ago
Feature Request
Password Visibility Enhancement
Enhancements: ● Toggle Feature Introduction: Implement an eye icon that users can tap to show or hide their passwords. ● User Guidance: Clearly label the icon to inform users of its function, enhancing overall usability. ● Accessibility Considerations: Ensure that the toggle feature complies with accessibility guidelines, allowing users of all abilities to benefit.
Vitaly Sokolovsky 1 day ago
Feature Request
Password Visibility Enhancement
Enhancements: ● Toggle Feature Introduction: Implement an eye icon that users can tap to show or hide their passwords. ● User Guidance: Clearly label the icon to inform users of its function, enhancing overall usability. ● Accessibility Considerations: Ensure that the toggle feature complies with accessibility guidelines, allowing users of all abilities to benefit.
Vitaly Sokolovsky 1 day ago
Feature Request
