We will move deadline for sure if no code update will be released next week, no worries, we will never force harsh migrations like this, and it seems we underestimated how people already used Pages.
3 Likes
How am I supposed to migrate the UI pages I have already created to the new Fibery app, if I cannot edit them? Am I missing something?.. I tried with Architect mode, and I also cannotā¦I already spent many AI credits and time on those pages, and now I have to do it again? Please, allow us to editā¦
1 Like
Note that we reset credits yesterday so technically you already have full credits till the end of this month. Even when we allow to edit files, old pages are incompatible with new apps and direct transfer is not possible
Manual code editing is coming, so you might want to hold off with wasting AI credits recreating existing AI pages.
Just wait til itās possible and then you can copy over the code from a page to an app. Then, if they donāt work perfectly, you can ask AI to fix any issues - probably will cost fewer credits than starting from scratch
1 Like
I will! Thanks.
Great. thanks!
Just wait til itās possible and then you can copy over the code from a page to an app
Thatās not fully correct. Page and App are not compatible. App is a React application, while Page was pure html.
One flow that might work is:
- you export your Page code to your filesystem
- you export empty App code to your filesystem
- you give your local coding agent system-prompt of an App Builder and Page Builder, so it knows how to build both
- you ask llm to recreate Page functionality as an App
- you import resulting App
This requires export/import api for an App plus knowledge of system-prompts.
Maybe this can be fully done in an App Builder UI, but will require some credits.
Anyway we do understand the transfer problem and will try give good instructions before Page sunset.
4 Likes
OMG. I thought there will be a notice on when the actual date of effectivity of the new AI credits. Just tried one query/chat and it ate 25 credits just creating 1 job description for a job role with almost all the information needed. I think, there should be optimization on the AI credit usages and this is a very big change to use that the credit eats sooooo much.
1 Like
This comment will be all over the place as Iām simply excited. This might be the greatest release ever. Canāt wait to try out different things, first test was highly successful.
Manual code editing will be another huge game changer, being able to test in real time and work with AI outside of Fibery (already used Opus 4.8 outside of AI to create the prompt after discussing what I want).
Actually testing this to show individual entities ā meaning customizable entity viewsā¦
Could someone please explain to me how this is completely client side, but I can create an App which another user can see? What does it mean in this context that the App is āClient sideā? How does another user see and interact with an App I created, whose files and code apparently lives on my client?
2 Likes
Hi Eren! Yes I can explain. It means that the code in these Apps runs all in the browser of the user viewing it, be it you or your client. So if you make a weather app, that pulls weather data from an API and you want it to register every time the temperature is above 30 degreesā¦ then it only does that as long as you have that App open.
If there would be server-side code then you could put that code there, so that independently if you have a session with your App open or not it could do the task you want it to do. Because the server always runs.
1 Like
And just to add to that, if your custom app is working with Fibery entities (which I imagine it will be for the majority of apps) the client-side code sends a query (makes an API call) to Fibery asking for entity data that it wants to display to the user.
If that app user does not have permission for that query, the request will effectively be rejected.
So a user might be able to āsee the appā (because it lives in a space they have access to) but not necessarily see the same things as you when they use the app.
So, the code is running client-side for everyone, but generating different results depending on who you are.
3 Likes
Also, to add. With just 3 chats. In my case it is just about doc creation already at near limit.
Can we have the option to remove the upgrade to pro banner. Like, we know we are poor and it hurts to see that all time for the rest of the month reset reminding us we are poor.
6 Likes
This is coming in July I hope, we will make it easy to develop apps in your code editor
3 Likes
BTW, we also have plans to allow Custom Entity View creation via AI
3 Likes
Will apps be viewable for the public when the space is shared on the web? So for users without an account?
āBTW, we also have plans to allow Custom Entity View creation via AIā WHOOP!
2 Likes
Yes, since it is a View it works as other Views
How do we do this?
That would be awesome! However, Iāve been testing but havenāt gotten it to work. My space is shared the web. I made an app there that works when logged in.
However, when I test if I can see the app, and I only see a blank page when I test it using another browser (not logged in) or incognito mode.
And considering the data itself, I asked the AI if it can make the data publicly accessible and get this response:
Also, can we please switch models / start a new chat to edit an app? I started an app using Opus before I saw your suggestion to use Sonnet. It did a great job getting a relatively complicated app put together. Now I just want to make tweaks, but I canāt switch away from Opus and I canāt just start a new āeditā chat. It makes it where itās hard to edit because I have to balance burning through a ton of tokens. It would be very helpful to be able to start with Opus for a relatively complicated layout, then switch to Sonnet for edits.
That said, the custom apps is unbelievably amazing.
1 Like
Unfortunately it is not possible, Anthropic managed agents limitation, so we canāt do that till they will allow it