Feedback on the Creation building process

I am developing an authenticator app and encountered several areas for improvement during the development process. I would like to share my feedback here.

  1. Rabbit Intern’s Limitations

The Rabbit Intern cannot produce a bug-free app on the first attempt.

To address the issues in the initial version, I need to provide follow-up prompts directing the Intern to make modifications and fix the existing problems. However, each follow-up prompt consumes a task count.

It would be more practical to treat the app creation process as a single Intern task, regardless of the number of follow-up prompts required. To ensure fair usage, we could introduce a limit (e.g., three follow-up prompts) per Intern task.

  1. QR Code Scanning Issue

In my original prompt, I specified that the app should include the ability to scan QR codes for importing OTP accounts and secrets. However, the first version of the app failed to implement QR code scanning correctly.

When I highlighted this issue in a follow-up prompt, the second version invoked the camera for scanning but caused the app to crash. To conserve my task count and create a functional app, I ultimately asked the Intern to remove the QR code scanning feature and rely solely on manual input for importing OTP accounts.

Question: Is QR code scanning a supported feature in Rabbit Intern’s creations? If so, how can it be implemented correctly?

  1. Persistence Issues

In the first version, I discovered through inspecting the source code that the app was using localStorage for data persistence. However, the OTP data was not retained when I relaunched the app on my R1 device.

To address this, I investigated how the “post its” creation handled persistence and discovered it used IndexedDB. IndexedDB worked well on the R1 device, so I requested the Intern to switch to IndexedDB for persistence in the app. This resolved the issue.

Suggestion: Either ensure localStorage works correctly on the device or make IndexedDB the default storage method for data persistence in all Rabbit Intern task for creations.

Finally, I would like to share my authenticator app.

1 Like

'm sorry to say that I’m extremely disappointed with this creation system, is not fair, the system is wrong, I paid for 3 working tasks, where there is a statement that the tasks may not be working or not work as I, who paid, asked them to do, the task consists of making an APP and the task ends when the app is successfully created even if it took multiple sessions because it is part of the same request, it is inconceivable that I should spend money to correct the errors made by your AI to create what I asked, I paid for 3 tasks and I only have one app that does not work as it should so I paid for nothing, a system like this is inconceivable, the system created me a broken app Even though I explained step by step and in detail to avoid misunderstandings what I wanted, then he used the remaining tasks to try in vain and uselessly to correct the errors made, in the end the result is that I paid $30 for an app that does not work

1 Like

He gastado 3 créditos en intentar crear una aplicación para ver el precio de la luz en España y no hay manera, o no funciona o se inventa los valores y las horas, De hecho la voz dice getting a random number between 200. Es un despropósito, una creación de una app debería consumir un crédito hasta que funcione.
Por otra parte estaría bien tener un buscador de apps, ya que posiblemente esté gastando créditos en crear una app que ya existe.

1 Like

I also found the creations mode frustrating as I used all my credits trying to fix issue with the app it created and wasn’t aware that these were considered new tasks. It should be that the app is not finished until finalised without deducting more credits to complete it.

I have been unsuccessful in being able to scan qr codes to load other creations a limited to only publicly shared ones as result.

Would also be good if people could collaborate on creations to fix bugs.