AI Usage

AI Chatbots: For quickly finding information on the railway I am not familiar, still manually checking through the responses and refining them to better fit my vision for the app. I prefer to not use this method especially for gathering large amounts of information such as station names or train units used in the internal database due to how often AIs like to hallucinate, so lots of my own time also goes into finding my own sources that I find reliable. The majority of features of Rail Index are my own ideas since I do not trust AI's enough to visualise what my app should look like or how it should be used. AI Developer: Unfortunately this is the only option for me to create this app, I do not have the skills myself and I absolutely cannot afford for someone else to do it for me. I never set out to create an app that I would spend so much of my time on, I just wanted to try out something I kept seeing ads for and I very quickly came up with the type of app I'd want most. Rail Index started as a simple prompt to Base44, asking for three quick and easy pages (overview stats, train logging and a submitted log table), the result of this prompt was so much better than I ever expected, so I kept coming back to add more and more features. You can see how that has turned out, despite my preferences of not using AI, I love what it has created for me to be able use myself and to share with you. AI Agent: For each published update, I always prompt Base44 to update the in-app AI support agent, I doubt it will ever get much use, but it is surprisingly capable of helping learn the apps features and to automatically submit logs on your behalf without going through the full logging page. It is however not a full replacement for actual support and it never will be - for any issues or feature requests, please visit the Contact page.