> This weekend I’m working on mobile app that allows you to upload photos and it turns everything into a stitched anime (ghibli or not) with movements and eventually sound and script. Great to make mini animes from your day or travels or anything.
I vibe coded the above including everything: code, design, logos. Just did it solo. It has all error handling, video generation notifications (it takes a while) and credit system. I myself can't believe it's been done in a month with AI. It's already in closed beta in iOS and android app stores. Let me know if you want to try it out before public release.
My quoted comment above was 28 days ago. This is working on this part time and with a family.
This weekend I’m working on mobile app that allows you to upload photos and it turns everything into a stitched anime (ghibli or not) with movements and eventually sound and script. Great to make mini animes from your day or travels or anything.
not to hijack this thread but my dad did extensive research in sea breeze and rainfall modeling and he would have loved to see these AI and machine learning advancements in weather prediction.
working on cursor for desktop. why rely on AI agent that’s self-contained when it’s limited, can’t access the browser, can’t open apps or click around.
i simply want mine to be able to fill in forms in preview with a passport image as context. also to be able to do recurring tasks as if i was the desktop user. e.g., i’m going to bed keep working on this spreadsheet.
it’s working and built but very slow and buggy atm. uses multimodal LLMS and OCR but lots more optimizations needed. need to make it a lot faster. can demo it and need help if anyone is interested.
i've worked on many legacy code bases and i think an underrated skill that you need is courage.
courage to be able to push changes you think could be breaking changes but always be optimistic that you to be able to fix as soon as possible. tests are ideal, but not everyone has 100% coverage. sometimes you just have to trust your gut and do diligence and push the change. don't be scared to push something because you don't know the behavior in production. the only way to know is to try.
Agree. But you need confidence on being able to debug / log / fix / revert, so having a strong knowledge of some of the parts is mandatory (i.e. server if it's web-dev, etc).
reminds me of the anthropic claude jailbreak challenge which only pays around $10,000. if you drive the price up, i'm pretty sure you'll get some takers. incentives are not aligned.
I'm a CTO and scaled multiple companies from zero to multiples of TBs of data (also to millions in revenue). I also worked on companies such as yourself that have an existing solution and want to revamp their entire technology base.
The short answer is yes, you should hire an in-house team so you can execute faster and also reduce the red tape of the provider not being more proactive.
How to do this is more nuanced:
1. I would start by documenting and/or asking for documentation on how the whole system works. This is key. I would start with a high level diagram. Even if you're not technical, this would allow you to evaluate the existing stack and see what could be worked on in parallel to the existing tech if any. I feel like you are technical enough to understand this since you understand CRUD and other terminologies. You can even set a time for the provider to explain the services to you if needed. I say parallel because I'm assuming you can't just quit using the system entirely, it will need to function until you do the switchover.
2. Once you have a good understanding of the system, this will allow you to be more specific on your needs. I almost never recommend a re-write but based on the statement that you are using a third-party product, this might be the case here. If it is indeed a re-write, I would approach it so that it's 1-1 parity with the existing system first, and if not, maybe with some ample planning and product grooming make the features even better. Furthermore, this will allow you to make a basic PRD for the requirements of what you are building. Doesn't have to be really specific but it will make it clear to yourself and others on what the task would be.
3. Hiring. At this point, I would start hiring a CTO/VP/senior engineer. Describe the problem from 2., maybe deep dive even if needed and start to get technical leadership going. I'm assuming cash is not a problem so if you start at $175k/year salary (maybe some stock/benefits) you can find many technical leaders that would go for this. Once you make that first hire, if they have a good network and or social clout it should be easy for them to hire people and/or consultants to do the job.
4. Iterate. Once you have that amazing team and if they have a good process in place they should keep iterating on the product and continue doing this on a steady pace.
5. Once the product is ready or any point that is it deployable make the switchover. At this point, you should have full in-house control of the product and have competent tech team in hand to do whatever is needed.
NVDA market cap for sure is bonkers but AI is here to stay. Anytime you question the future, think if you can see yourself in "that" future. For me, AI is already a part of my workflow and it's beneficial to my daily life. From coding, explainers, and to random questions in perplexity.
In coding, it made me a lot more productive. No more do I have to scour Google or Stack Overflow. Instead, I get the answer straight from the AI. It might not be working at times but it's definitely better.
Even random questions like "What is the cost to produce the Apple Pro Display XDR?" is being answered more promptly by AI.
This is contrary to the crypto craze where there was expected use but sadly it did not come to fruition. And until now, it's still a speculative industry, a solution looking for a problem.
alternatively you can get away from the app size bloat by using X as a PWA (progressive web app). in iOS, this would use safari as the app container and you would just have the assets to download for dependencies. it's sad however that apple is now trying to kill PWAs. i wish people would use PWAs more as this actually makes it easier to build apps.
i really hope they don't as it does provide an acceptable alternative to native apps. not everyone has a mobile team that can build native. imagine a small team just making a web app could now also provide a similar experience and value for mobile out of the box.
While I don’t vote and I don’t necessarily disagree, I think that going for the web version of Twitter is probably the wrong decision unless one of the following is one of your primary concerns:
* Your phone has so little free space on it that you use the web version, and periodically clear any data it builds up in your browser
* You are concerned with the increased tracking area that the app exposes
* You run web extensions that alter the Twitter experience
For most other usecases (features, battery life, accessibility) the website is probably the wrong choice. I suspect this will remain the case until the native app gets an inevitable rewrite when X decides they don’t want to maintain it anymore.
Is facil.io maintained? Last commit was 2 years ago, which is a bit concerning for something written in C that handles a bunch of security-sensitive things including a from-scratch JSON parser.
I vibe coded the above including everything: code, design, logos. Just did it solo. It has all error handling, video generation notifications (it takes a while) and credit system. I myself can't believe it's been done in a month with AI. It's already in closed beta in iOS and android app stores. Let me know if you want to try it out before public release.
My quoted comment above was 28 days ago. This is working on this part time and with a family.
EDIT: Added context.
reply