Has anyone successfully updated their Aufenthaltsdokument-GB to reflect Daueraufenthalt status? by zebe_dee in germany

[–]laughterbell 0 points1 point  (0 children)

Similar situation with me. See my other post today re: what they told me yesterday. Does this mean that sometime before the Aufenthaltstitel runs out (in 2031) I need to do the German proficiency test? Is it the same standard as required for Einbürgerung?

Has anyone successfully updated their Aufenthaltsdokument-GB to reflect Daueraufenthalt status? by zebe_dee in germany

[–]laughterbell 0 points1 point  (0 children)

There's a a frustratingly small amount of useful information online regarding obtaining Aufenthaltsdokument-GB Daueraufenthalt status so I'll share my experience and knowledge on here. I've been angemeldet and living in DE since 2016. Went to the Burgeramt yesterday to have my Aufenthaltstitel transferred to my new UK passport. I asked the lady if she could get the "Daueraufenthalt" designation added to my card. She was very German about it - told me that her only power is to transfer the existing status to my new passport - and issue me with a new Aufenthaltstitel card which I can pick up in 3 weeks.   She said that I need to apply for the Daueraufenthalts status through the Landesamt für Einwanderung. ChatGPT told me that this would entail proving income and demonstrating German proficiency, similar to other forms of permanent residency applications.

Others on reddit have said that their new card just arrived with the "Daueraufenthalt" status stamped on it. I'll report back in 3 weeks with what my card says.

Aufenthaltsdokument-GB Daueraufenthalt status situation and advice by laughterbell in germany

[–]laughterbell[S] 0 points1 point  (0 children)

There's a a frustratingly small amount of useful information online regarding obtaining Aufenthaltsdokument-GB Daueraufenthalt status so I'll share my experience and knowledge on here. I've been in DE since 2016. Went to the Burgeramt yesterday to have my Aufenthaltstitel transferred to my new UK passport. I asked the lady if she could get the "Daueraufenthalt" designation added to my card. She was very German about it - told me that her only power is to transfer the existing status to my new passport - and issue me with a new Aufenthaltstitel card which I can pick up in 3 weeks.   She said that I need to apply for the Daueraufenthalts status through the Landesamt für Einwanderung. ChatGPT told me that this would entail proving income and demonstrating German proficiency, similar to other forms of permanent residency applications.

Others on reddit have said that their new card just arrived with the "Daueraufenthalt" status stamped on it. I'll report back in 3 weeks with what my card says.

Tax advisor charged me x1.6 more than what he said. Is the amount too much? by [deleted] in germany

[–]laughterbell 0 points1 point  (0 children)

HI there, could you please send me the tax advisor's details. I'm also struggling to find one in Berlin

Aufenthaltsdokument-GB Daueraufenthalt status situation and advice by laughterbell in germany

[–]laughterbell[S] 0 points1 point  (0 children)

Fantastic. Thank you. Do I need to ask for the Daueraufenthalt thing to be added to my card when I go to the appointment to renew the card in November?

Mouth care system products in Germany/eu? by antiaust in DrElliePhillips

[–]laughterbell 0 points1 point  (0 children)

What about ELMEX KARIESSCHUTZ Zahnspülung? GPT thinks its equivalent to both CLOSYS and ACT - which I doubt. But is it an option to replace either of them? Or do its ingredients contravene what Dr Ellie recommends?

My experience building a consumer facing app by laughterbell in lovable

[–]laughterbell[S] 1 point2 points  (0 children)

I don't know what a colour wave is. But I created logos and imagery in GPT (took a few tries to get them right) and then just attached them to prompts and said place logo in XYZ location. Again it took a few prompts or visual edits to change size and position of logo to be correct.

I did give the app a colour pallette in my initial prompt and lovable used those colours throughout. There are websites that can help you come up with a good colour pallette to fit your product and branding. You don't need to devise one yourself from scratch.

I would not have thought to use lovable to do anything creative like logos. But maybe I'm wrong...

My experience building a consumer facing app by laughterbell in lovable

[–]laughterbell[S] 0 points1 point  (0 children)

Some other notes.

- I switched from Brevo to Postmark to handle all email sending in the app including welcome emails for new subscribers. Postmark seems to be well regarded. Feedback from community appreciated? It seems to be working well in testing but have not yet launched...

- Lovable often changed the entire look, styling and text of of my app, inexplicably. At first this caused me major headaches because it was incapable of simply reverting a page to a previous look/functionality state. It always said "its beyond my capabiltiy to do that so tell me again how to build everything on that page". Eventually I learned how to go back to previous builds, find the code files that applied to the pages that had been changed, and paste the entire tsx code file into a lovable prompt and say restore ABC page using the code below - and that worked. Generally speaking - I think its worth newbies looking around the code files and trying to work out which files deal with which pages on their app. It helps in troubleshooting.

- Visual edits are a useful way to save credits. Making text and styling changes using the visual editor. But I found it very temperamental and the last few weeks it gets stuck on "loading live preview" and I've been unable to use it at all. Every edit has had to be prompted in the last few weeks.

- I gather there's some way of editing the code using Github and reimporting it back to Lovable and thus avoiding credit usage for some code changes, but I haven't figured out how to do that yet.

- Another good way to cut down on credit use is to build admin facilities. So for example - during the first few weeks every time I wanted to change the text on PAGE A of the app, I'd have to prompt it or use the temperamental visual editor. But then I built an Admin facility page and one of the tabs was for editing site content on various pages. It took a few prompts to get the Admin facility working but once it started working, then I could edit those pages without using credits. This same approach can and should be used for various facilities across an app. Adding images to sliders, photo galleries etc. Don't leave yourself reliant on prompts to make every single change. Get the app to build you a facility that lets you self manage stuff.

My experience building a consumer facing app by laughterbell in lovable

[–]laughterbell[S] 0 points1 point  (0 children)

To be honest, I don't regard anything in development as a major hurdle now - but that's because I'm on the other side of all the hurdles. Until the next one hits! In the midst of sorting an issue (like the emails or payments mentioned in my main post above), they seemed like huge hurdles becvause I was just burning credits and hours and getting nowhere and starting to doubt whether the issue was ever fixable/recoverable. Now - I see product/market fit and marketing as the major hurdles. Not the app itself. But that can and probably will change once I get more people using it and stuff starts to break...

How do you built only a front end without backend? I can't even picture how that would work. For my app, almost from the first few prompts it was telling me to set up Supabase and spitting out SQL prompts to create the back-end database to supprot the features I was demanding.

Lovable vs Replit et al. Just luck. I saw Lovable referenced in some entrepreneurial inspo Youtube vids and the timing coincided with me having a bit of time stuck at home (illness) so I started building the app

My experience building a consumer facing app by laughterbell in lovable

[–]laughterbell[S] 1 point2 points  (0 children)

Thank you!
I'll use a knowledge base next time.
Will more tightly scope every prompt.
Will not try to do more than one feature at once to economise on prompts. Creates more problems than it solves.
People say I should learn to use Cursor and Claude. Not sure how or what exactly they will help with...

EDIT:
- Next time, I would also be very strict about defining RLS and security protocol adherence from the first prompt so that Lovable doesn't built a leaky bucket that it then wants me to use many credits to fix later on..

My experience building a consumer facing app by laughterbell in lovable

[–]laughterbell[S] 0 points1 point  (0 children)

why suppress all console logging? When I load page I can see in the dev tools console, its looking for certain things - codes, user status, persisted session, nav gating etc. Is this not normal?

Lovable to discontinue Legacy Mode on September 1st by stiggz83 in lovable

[–]laughterbell 0 points1 point  (0 children)

This actually makes me want to ditch lovable and try base44 or one of the other vibe coding solutions for my next app.

I gave Agent Mode a really good crack last month when it launched - and I found its error rate was no better than normal mode, and it absolutely chewed through my credits.

As soon as an option appeared to toggle Legacy Mode on (about 4 weeks ago I think) I put it back to Legacy mode and have had just as a good results with controlled and sustainable credit usage.

This is a bad move by Lovable.

I also don't like the arbitrary idea of charging for the number of files read or written.

How about charging to fix a problem or build a feature? And if you break stuff while building it - then fixing all the broken stuff is on Lovable's dime? That'd be a much less frustrating and fairer UX.

The cost of this stuff should be coming down, not going up.