Artificial Intelligence Blogs Posts
cancel
Showing results for 
Search instead for 
Did you mean: 

This is part of the August Developer Challenge on Joule Studio.

SAP and Vercel have partnered to enable developers to build lightning-fast, modern frontends (using React and Next.js) for enterprise applications and AI agents, while securely connecting to SAP’s robust backend infrastructure in the newly announced Joule Studio. Vercel will become available within Joule Studio to give developers an unparalleled choice for custom frontend design. Hence, now let’s understand what Vercel, Next.js and v0 are, how they are connected to each other, and how they relate to the new Joule Studio. 

image.png

 I. Next.js: 

Next.js is a React framework for building full-stack web applications. Created by Vercel, this framework takes the power of React.js which is a popular library for building dynamic user interfaces, and supercharges it with features like server-side rendering (SSR), static site generation (SSG), and a built-in routing system, all out of the box. Developers can rapidly build highly flexible, custom web interfaces using popular frameworks like Next.js using the new Joule Studio platform. 

Let's create a new Next.js app from scratch to see it in action: 

1. System requirements: 

  • Minimum Node.js version: 20.9, install from here: https://nodejs.org/en/download . Check with node –v  command on your terminal to see the current node version installed.
  • Operating systems: macOS, Windows or Linux 
  • Git installed 
  • VS Code or another code editor with integrated terminal or a standalone terminal such as PowerShell on Windows or Terminal App/iTerm on Mac OS 
  • A GitHub Account 

2. Run these commands one by one on the terminal: 

npx create-next-app@latest business-card-app --yes 
cd business-card-app 
npm run dev 

npx is a powerful tool bundled with Node.js that executes JavaScript packages directly from the registry without requiring you to install them globally 

create-next-app is the official command-line interface (CLI) tool used to instantly bootstrap and set up a new Next.js application 

npm is a command-line tool used by developers to install, share, and manage project dependencies. It is automatically installed whenever you download Node.js. 

--yes skips prompts using saved preferences or defaults. The default setup enables TypeScript, Tailwind CSS, ESLint, App Router, and Turbopack. 

3. Open the project folder in VS Code and observe the folder structure (app, public folders): Next.js uses file-system based routing, meaning you can use folders and files to define routes. 

  • View the code in the layout.tsx file contents in the app folder 
  • View the code in the page.tsx file contents in the app folder 
  • View the package.json file contents at the root level 

 A .tsx file is a TypeScript source file that contains JSX, an XML-like  syntax used to describe UI in React.  

 4. Replace the contents of the page.tsx with the below content 

5. In the newly updated page.tsx code, scroll to the bottom of the file. 

  • Search for type="hidden" within the form tag in the page.tsxReplace the hidden values for communityId with your SAP Community username by updating the value attribute
  • Replace the value attributes: 
    • communityId: your SAP Community username 
    • answer: your answer to the below question (one word answer)
    • week: keep as "week4" 

S-User, P-User, the email associated with SAP Community portal are not valid Community Ids. To get your SAP Community Id, follow the instructions as per the screenshot below. 

community_id.png

Question: When frameworks use server-side rendering, the server delivers raw, non-interactive HTML to the browser. Name the process that attaches event listeners to this static HTML inside the browser to make the page interactive. 

  • View the business-card-app at the http://localhost:3000 url 
  • Stop the local development server by pressing Ctrl+C (Mac/Windows/Linux) in the terminal before continuing to the next steps. 

 6. Commit and push these changes to your GitHub repository. In the next step, we shall deploy this app to Vercel.  

II. Vercel 

Vercel is a cloud platform for developers that provides the infrastructure to host, build, and deploy web applications instantly. You can easily link your GitHub repository to Vercel and deploy those GitHub projects. Once deployed, you can view your site/app from a live URL hosted on the Vercel platform. 

1. Sign up to the Vercel platform from https://vercel.com/signup 

shrinivasan_neelamegam_0-1784808862746.png

2. Choose the Continue with GitHub option and use the same GitHub account that you pushed your repository to in the previous step. Once logged in, add a new project using the Add New option in the top right corner. 

shrinivasan_neelamegam_1-1784808862746.png

Here is a short video showing how to link your GitHub repository to Vercel https://www.youtube.com/watch?v=GthkPo8xFqQ 

3. Your newly created GitHub repository is available for import to Vercel. Click on Import. 

shrinivasan_neelamegam_2-1784808862746.png

4. Expand the Environment variables and provide the CAP_SERVICE_URL as 

https://community-challenge.cfapps.us10.hana.ondemand.com and Click Deploy. 

shrinivasan_neelamegam_3-1784808862746.png

5. It only takes a few minutes to deploy your app. You could notice how easily you were able to deploy an app to Vercel. As soon as it is deployed, your site is live. You will be able to view your business card app with a URL unique to your deployment. 

shrinivasan_neelamegam_4-1784808862747.png

6a: Test Your Deployment (Required) 

  1. Launch your Vercel URL in a browser 
  2. Click the SAP Community button to submit your Week 4 answer 
  3. You should see a success message confirming submission 
  4. Post a comment on this blog post with: 
    • A screenshot showing your deployed business-card-app URL in browser 

6b: Enhance Your Card (Optional ) 

Want to customize further? Edit lines in page.tsx containing: 

  • Your name and title 

Commit and push to GitHub. Vercel auto-deploys changes in less than 2 minutes. Refresh your Vercel URL to see updates. 

7. Add a comment answering at least 2 of these: 

  • Ease of use: How smooth was Next.js setup and Vercel deployment? 
  • Pain points: Where did you get stuck or confused? 
  • Comparison: Do you use React/Vue/Angular or Netlify/AWS Amplify or some other tool that does something similar? How does this compare? 
  • Future use: Would you use Next.js + Vercel for your projects? Why/why not? 

III. v0 in Vercel 

v0 empowers anyone to build functional web applications faster without writing code manually. v0 generates production-ready UI components and frontend code, utilizing a modern web stack that includes Next.js, React architecture, Tailwind CSS, shadcn/ui, and the Vercel AI SDK. The code generated is ready to be deployed on the Vercel's globally scalable infrastructure. 

What is Vercel's relationship with v0?  

Vercel created v0 and provides the underlying infrastructure. This deep integration enables one-click deployment to enterprise-grade infrastructure, adhering to compliance, strong security, and global scalability. v0's code is optimized for the Vercel platform, ensuring a smooth path from idea to production.  

In the first Next.js exercise, you manually created the app and updated the page.tsx with the code provided in the exercise. You would further enhance the pages by editing the code manually without v0.  

With v0, you will be able to provide prompts to create such UIs or modify existing code imported from an existing GitHub repository.  

Joule Studio embeds Vercel's vibe-coding platform v0 natively in the browser, so users can generate modern, powerful React/Next.js front-end applications without ever leaving the Studio. 

This exercise below about v0 is an optional exercise. We included it here because v0 is the key part of Vercel that will be embedded into Joule Studio. 

Note: Though vibe-coding is a key feature in v0, we are not asking you to do vibe-coding in this exercise because you get $5 credit per month in the free trial account and you would likely expend that very quickly. 

Optional Exercise: 

  1. Open the url https://v0.app/ in a browser 
  2. You will see a text area where you can provide your prompt to vibe-code your app idea.  
  3. Just below the text area, you will see the already available templates of the sites built by vibe-coding with v0 
  4. Open the template with the title Optimus - The AI platform to build and ship and scroll through the page and access various tabs within this site 
  5. Custom landing pages such as these can be created with vibe-coding on the v0 app. You can also use v0 to build anything, from landing pages, dashboards, e-commerce stores, and AI apps to full-stack applications.

In short: 

Vercel provides the deployment and hosting platform, while v0 is the AI-powered vibe-coding tool used to generate React and Next.js applications from natural language prompts.

 

 

 

 

 

 

 

39 Comments
nanda_kishore_27
Explorer

Week 4 Submission

nanda_kishore_27_1-1787548370756.png

  • Ease of use:  Really easy and super fast  
  • Pain points: No it was very clear and easy to use 
  • Comparison: Always been a UI5/Fiori CAP developer , compared to our mta build and deployment times this was super fast , but given this is is just a light weight front end app it was expected ... would like to know how quick and easy would it be to deploy a full blown full stack app on vercel
  • Future use:  Definetly will try to use , it looks simple and elegant but would like to explore all posibilities that vercel brings first ...

    how does this fit in SAP world ?
    Is it something our agents can use to show UI , how does this fit in Joule studio 2.0's agent building capabilities ?
    W
    hat can we do in joule studio with vercel and v0 , is it something joule studio internally uses or something developers should use to extend out of box UIs from Joule studio created agents....

    Lot of questions 🙂
    Will have to wait for Joule studio 2.0 trail to try out and know more
Muthu031
Explorer

Muthu031_0-1787554067228.png


Hi @shrinivasan_neelamegam ,

Thanks for introducing Vercel and v0 in August month week4 challenge.

  • Ease of use: Vercel platform is simple and easy to use, deployment takes less than a minute(week 4 exercise). Adding v0 is very useful, reduces development efforts.
    • Vercel Platform - Reduces Deployment complexity.
    • v0 - Reduces Development complexity.
  • Future use: Need to explore destination, connectivity, SSO, and other concepts. Looking forward for real time examples connecting SAP system.

Thanks,

Muthu.



ankur_gandotra2
Advisor
Advisor

https://business-card-fasmtce8i-i072354s-projects.vercel.app/

ankur_gandotra2_0-1787558743497.png

ankur_gandotra2_1-1787558761090.png

The Next.js setup was quite smooth. Creating the application with create-next-app was straightforward, and the development server was up and running within minutes. Vercel deployment was also very simple once the GitHub repository was connected, and the automatic deployment after pushing changes was particularly convenient.

The main pain point was GitHub authentication during the initial push, since password-based authentication is no longer supported and I had to use browser-based authentication.

Overall, I would definitely consider using Next.js + Vercel for future projects, especially for applications where a modern frontend, fast deployment, and easy CI/CD are important. The developer experience from local development to GitHub and production deployment was very smooth.

SenaNttData1
Explorer

image-1787557553020 kopya 2.pngDeployed: https://business-card-app-delta.vercel.app

 

Ease of use: the scaffold-to-live path is genuinely short. create-next-app, replace one file, push, import, deploy - the only real configuration was the CAP_SERVICE_URL environment variable, and skipping that is the one thing that silently breaks the button (the server action throws "CAP_SERVICE_URL is not configured" rather than failing visibly on the page).

 

Pain point: not Next.js itself but npm. My first install raced with the one create-next-app runs, so node_modules/next existed while node_modules/.bin/next did not, and npm run build failed with "next: command not found" - which sounds like a missing package but is not. Deleting node_modules and package-lock.json and reinstalling fixed it. Worth knowing before you start debugging the wrong thing.

 

Comparison with Week 3: both weeks end at the same CAP endpoint with the same payload. In Week 3 the n8n Code node built the whole page as an HTML string and the form ending served it; here the same idea is a real React component with a server action. Coming from ABAP, the Vercel side felt closer to normal engineering - the output is a repo you can read and version, and pushing to main redeploys in under two minutes.

 

And since this is the last week - thank you to Rekha D R, Dan Wroblewski and Shrinivasan Neelamegam for putting the month together. Going from a course, to an n8n workflow, to a deployed frontend in four weeks was a good arc, and having the same CAP service at the end of each one made it feel like one thing rather than four separate exercises.

denismih
Product and Topic Expert
Product and Topic Expert

Screenshot 2026-08-24 at 11.09.47.png

Ease of use: Very nice and smooth experience

Pain points: I was stuck with corporate git, didn't find a way to connect it to Vercel

Future use: It is very interesting how it will be connected to SAP internal infra. Can't wait to try it!

Cocquerel
Active Contributor

Ease of use: the small challenge was easy but I have not enough experience to evaluate how easy that will be with real project
Pain points: My change was not automatically reflected in Vercel platform after updating my github repository. After some time or maybe because I have trigger a manual redeployment, it was finally reflected.
Future use: I wonder what is the SAP strategy in introducing Vercel / Next.js instead of using CAP / SAPUI5 framework. I'm also wondering how it will integrate with components like Workzone, Joule Work, S/4HANA,...
vercel.png

Dan_Wroblewski
Developer Advocate
Developer Advocate

Dan_Wroblewski_0-1787562989703.png

 

sasbro
Explorer
  • Ease of use: Out of the box. Setting up an account with 2FA needed more effort than deploying.
  • Pain points: Nowhere.
  • Comparison: Angular in the past, but Next.js is more modern and simpler (imho)
  • Future use: For personal small projects of course

 

sasbro_0-1787565977071.png

 

Klingbeil_Thorsten_swm_0-1787567150734.png

Hello @shrinivasan_neelamegam,

great Challenge - I really enjoyed it!

  • Ease of use: Vercel is simply wonderful! easy, fast, great DX
  • Pain points: Tailwind was not installed and integrated right from the start - maybe i missed it during the app init
  • Comparison: we're using BTP (CF) with HTML5-repo and UI5 Apps 
  • Future use: would use Vercel / Next for certain use-cases (e.g. consumer-apps)

br & thx!

Thorsten

JensR
Advisor
Advisor

week4.jpg

  • Ease of use: really simple!
  • Pain points: searching for my github.com credentials was most pain 🙂
  • Comparison: normally using CF with CAP&UI5/Fiori. This looks much nicer
  • Future use: Definitely want to try it. But let's see how it is integrated in new Joule Studio...
FerCucci
Explorer

Deployed and submitted, result Accepted.

Screenshot 2026-08-24 at 14.28.06.png

App: https://business-card-app-gules.vercel.app/
Repo: https://github.com/fernandocucci/business-card-app

Ease of use: The setup was fast. create-next-app gave me a running project in a minute, and the Vercel import detected the framework by itself. The only manual step was the CAP_SERVICE_URL environment variable. After that, every push to main redeploys automatically.

Comparison: my usual front end work is SAPUI5 and Fiori elements on BTP, deployed to Cloud Foundry or the ABAP repository. Next.js on Vercel removes almost all of the build and deploy configuration. The trade off is what UI5 gives for free: OData V4 model binding, Fiori elements floorplans, and launchpad integration.

One question for the SAP team: with Vercel and v0 arriving in Joule Studio, what is the recommendation for choosing between SAPUI5 and Next.js in a new project? Is Next.js meant for customer facing and AI agent frontends, while UI5 stays for launchpad and core transactional apps, or is the scope wider?

KalEl
Discoverer

KalEl_0-1787574864699.png

An SAP challenge that felt the least like SAP of any of them so far 🙂 — and I mean that as a compliment.

  • Ease of use: Very smooth. Pushing to GitHub triggered an auto-deploy that was live in about two minutes without touching anything.
  • Pain points: The environment variable handling. CAP_SERVICE_URL is not bound to the individual deployment I created — it is defined at the project/environment level, so every deployment in that environment inherits it.
  • Future use: Yes — specifically for customers who want a more modern, visually richer UI than Fiori gives them.

Hello everyone,
2026-08-24_21h36_16.png

  • Ease of use: The Next.js setup and Vercel deployment were very smooth and fast. Connecting the GitHub repository to Vercel was straightforward, and every push automatically triggered a new deployment.

  • Pain points: The main point I needed some time to understand was the difference between Server Components and Client Components, especially when "use client" is required. Apart from that, the overall process was clear and easy to follow.

  • Comparison: I mainly work with SAPUI5, CAP, and SAP BTP. Compared with the MTA build and deployment process to Cloud Foundry or the HTML5 Application Repository, Vercel felt much faster and simpler for a lightweight web application. However, SAP BTP remains more suitable for enterprise scenarios requiring authentication, destinations, governance, and deep S/4HANA integration.

  • Future use: I would definitely use Next.js and Vercel for prototypes, hackathons, public websites, and standalone AI applications. For enterprise SAP projects, I would evaluate Vercel, SAP BTP, or a hybrid architecture depending on the security and integration requirements.

Best Regards,
Huy Nguyen Hoang Thai

S0012164523
Explorer

 

S0012164523_1-1787582812165.png

  • Ease of use: Very Nice and smooth to use and deploy
  • Pain points: I've been confused in Environment Variable but got it from settings later. It was so easy to find

Waiting to see it in Joule studio

hrushikeshraju_yerram_0-1787583635734.png

Ease of use: Vercel deployment was simple because it can directly connect to a GitHub repository and automatically build and deploy the Next.js application.

Future use: I would definitely prefer using vercel and v0 for my future web application projects. Very easy deployment and AI assistant for UI creation.

cristiansolisc
Explorer

Week 4 done. Deployed to Vercel, submitted, result Accepted. Screenshots below.

Ease of use: about ten minutes from create-next-app to a live URL. The only manual step was the CAP_SERVICE_URL variable.

Future use: yes, for anything customer facing where Fiori would be too heavy. For core transactional apps I'd still stay on UI5.

Thanks for the challenge.Week4_Challengue.pngWeek4_Challengue_2.png

bhupenderjeet
Advisor
Advisor

2026-08-24_16-02-27.png

  • Ease of use: Deployment was explained very well in steps and it was very easy go configure.
  • Pain points: I faced challenge while pushing the changes from local reposiotry to github. Github repo was getting the changes but vercel deployment didnt get the changes and got conflicts between my Personal and Enterprise github accounts. As a workaround i have to deploy a new project in vercel each time to incorporate my changes in repository. Though later i noticed the repository can be deployed directly in versel as well and github can be skipped.
  • Comparison: I have used netlify and its also very simple as vercel but vercel seems to have much more options. Looking forward to explore it more. 
  • Future use: Looking forward to use it in future especially eager to see how it integrates with Joule studio.
TinhLeo
Participant

Hallo all,
TinhLeo_0-1787584694742.png

 

  • Ease of use: Fast, seamless Next.js setup and Vercel auto-deployment via GitHub integration.

  • Pain points: Learning the distinction between Server and Client Components (when to use "use client").

  • Comparison: Vercel is much faster and simpler for lightweight apps compared to SAP BTP (MTA/Cloud Foundry). However, SAP BTP remains superior for complex enterprise scenarios (governance, security, S/4HANA integration).

  • Future use: Next.js/Vercel for prototypes, hackathons, and standalone apps. For enterprise SAP projects, a choice between Vercel, SAP BTP, or a hybrid approach will depend on specific requirements.

 

IanHuhn
Discoverer

IanHuhn_0-1787594200904.png

  • Ease of use: Next.js setup and Vercel deployment was really easy, even easier than SAP BTP deployment.
  • Pain points: I got stuck with the corporate Github blocking me from installing Vercel on my personal account (not allowed). Instead, I exported zip file and imported it. It's okay for the exercise but it should be avoided for production use. 
  • Comparison: Only comparison I can provide is with Fiori apps deployment on S/4Hana on-premise or BTP. I would love to have a similar experience on these.
  • Future use: As I am working mainly on Fiori apps, this kind of app/UI/architecture is completely out of our scope as we would lose all benefits we get from Fiori and ERP integration. However, for a use case completely unrelated with the ERP, why not, but we would need to have a specific team with enough skills to ensure quality, conformity and security of such an app, which is not the case currently.
i_Dani
Explorer

i_Dani_0-1787603523107.png

 

  • Ease of use: Next.js setup was pretty smooth, and Vercel made the deployment process really simple. Connecting GitHub and getting the app live was quick.
  • Pain points: I initially had some confusion around the Next.js project structure and environment variables. Once that was clear, the rest was straightforward.
  • Comparison: I’ve mainly worked with Angular, so Next.js felt more lightweight and flexible. Vercel also makes deployment much easier compared to traditional approaches.
  • Future use: Yes, I would definitely consider using Next.js + Vercel for future projects. The development and deployment experience is simple and fast.


    @shrinivasan_neelamegam Thanks for organizing this challenge—it was a great hands-on experience to explore Next.js and Vercel!

    Thanks to the August Developer Challenge team! Really enjoyed the challenges and the hands-on learning experience.
MAHERG
Participant

Hello Shrinivasan,
Thank you for this awesome challenge.

                                                        MAHERG_0-1787610803555.png

Ease of Use : The Next.js setup and Vercel deployment process were very smooth and straightforward.

Pain Points : Everything was well documented and clearly explained, so no significant pain points encountred.

Future Use : I’m looking forward to using these technologies in future projects, and I’m especially eager to explore how they integrate with Joule Studio.

Salomon_160807
Newcomer

Result.png

Reflection & Feedback
Ease of use: Setting up Next.js and deploying to Vercel was super fast and smooth once the repository was linked. Adding environment variables like CAP_SERVICE_URL directly in the Vercel dashboard makes managing server configurations effortless.

Pain points: The main friction point was configuring Git identity and authentication (Personal Access Token) in the Linux terminal to push the local commit to GitHub. Once the authorization was sorted out, the rest of the deployment pipeline was seamless.

Comparison: Coming from working with other enterprise frameworks and cloud setups, Next.js combined with Vercel feels much more streamlined for full-stack applications. The native integration of Server Actions simplifies handling backend POST requests without needing complex API boilerplate.

Future use: Definitely! I would use Next.js + Vercel for future projects. The automatic deployment on git push, combined with Server Actions and zero-config hosting, makes it a top-tier stack for fast prototyping and production deployment.

Submission Details
Result: Accepted

Community ID: Salomon_160807

Thanks for another awesome challenge! 🙌

dhineshkumar1030_39
Discoverer

I built and deployed a Next.js business card application using Next.js + Vercel.

Ease of use: The Next.js setup was straightforward, and Vercel made the GitHub integration and deployment process very smooth. The automatic deployment after pushing changes was especially convenient.

Pain points: The initial setup had a minor npm certificate issue, but after resolving the environment configuration, the application worked as expected.

Overall, it was a great hands-on experience understanding how Next.js, React, and Vercel work together to build and deploy modern web applications.

dhineshkumar1030_39_0-1787623330388.png

 

GuruDuttt_A
Participant

GuruDuttt_A_0-1787632373896.png
Thank you for such an amazing challenge . I added my personal touch to the business card. 
#week4 completed 🏆

lakshminarayana_J_0-1787639718075.png

Completed Week 4 of the August Joule Studio Developer Challenge🎉🏅.

This was a really good hands-on experience for me. I got to work with Next.js and React, deploy the application on Vercel, configure the SAP CAP service, and understand how hydration works with server-side rendering.

You can check out my deployed business card here:
https://aug-joulestudio-challenge.vercel.app/

A big thanks to @shrinivasan_neelamegam for putting together such a practical and useful challenge. I learned a lot by actually building and troubleshooting the application rather than just reading about it.

Also, thanks to  @Dan_Wroblewski  and   @Rekha_DR   for organizing the August challenge. Really enjoyed being part of it and learning something new throughout the month.

Successfully completed the August challenge, and now looking forward to TechEd, Devtoberfest, and many more challenges and learning opportunities ahead!

 

 

CarlosMarquez
Explorer

 

CarlosMarquez_0-1787647666647.png

 

  • Ease of use: How smooth was Next.js setup and Vercel deployment? 

It was simple and quick.

  • Pain points: Where did you get stuck or confused? 

  I had to redeploy because it didn't correctly recognize the environment variable.

Yash_Bhargava1
Explorer

My Week 4 Submission

Here is my deployed business card application using Next.js and Vercel!

Yash_Bhargava1_0-1787648334890.png

 

  • Ease of use: The Next.js setup was very straightforward using the create-next-app CLI. Vercel deployment was incredibly smoothonce I pushed my code to GitHub, linking the repository to Vercel handled the build and deployment automatically in just a couple of minutes.

  • Pain points: I ran into a few local environment quirks on Windows (specifically getting npm recognized in my system path) and learned the hard way that Git requires commit messages before pushing! I also had a minor hiccup ensuring my exact SAP Community ID was correct for the CAP service submission, but troubleshooting it was a great learning experience.

  • Comparison: As a Lead Technical and Integration Consultant, I am used to heavier, more complex enterprise setups. Compared to traditional backend-heavy deployments or standard SAPUI5 applications, the Next.js and Vercel stack feels incredibly fast, agile, and lightweight.

  • Future use: Absolutely! The zero-config auto-deploy pipeline from GitHub to Vercel is fantastic. I would definitely use this stack for rapid prototyping, building modern customer-facing frontends, or any project that benefits from server-side rendering and fast iterations.

AditiArora16
Participant

Screenshot 2026-08-25 at 10.57.17.png

Ease of use: creation to a live Vercel URL was fast and nearly config-free, aside from environment variables.

Pain points: CAP_SERVICE_URL worked locally via .env.local but never reached Vercel (env files are gitignored, not deployed), so the SAP Community button gave 'page not found errors' in production until I added it in the Vercel dashboard.

Future use: Yes, for small apps the setup-to-deploy speed is hard to beat, as long as I remember to sync env vars to the dashboard before shipping 😂

Pranay-sap-123
Discoverer

Pranaysap123_0-1787653052930.png

https://week4-sable.vercel.app/
all the links are correct

 

muthupandi_m
Explorer

 

muthupandi_m_0-1787656624238.png

Vercel Link : https://business-card-app-sigma.vercel.app/
Ease of use: This was my first time using Vercel, and honestly it felt very smooth for a first-timer. The whole flow from Next.js setup to Vercel deployment just worked without much friction.

Pain points: No real pain points to report — this was a completely new learning experience for me, and I genuinely enjoyed going through it step by step.

Comparison: I come from an ABAP development background, so tools like Next.js, React, and Vercel are quite new territory for me. It's been a while since I picked up a fresh skill set like this, and it was refreshing to step outside the usual SAP stack for a bit.

Future use: I'd definitely like to use these skills going forward, especially to build agents in the new Joule Studio. This exercise has given me a good foundation, and I'm looking forward to getting trial access to Joule Studio so I can put this learning into practice on real agent-building use cases.

Overall, this challenge gave me more than just a task to complete , it opened up a new area of learning for someone with a traditional ABAP background. Really appreciate the SAP team putting these challenges together, and eagerly waiting for the Joule Studio trial to explore further!

Bemasi
Discoverer

Bemasi_0-1787657947298.png

https://bemasi-week4-sap-august-challenge-alpha.vercel.app/

Ease of use

Next.js has a fairly gentle on-ramp thanks to create-next-app: one command gets you routing, SSR/SSG, and a ready-to-go folder structure. Deploying on Vercel (the company behind Next.js) is close to "connect the GitHub repo and you're done" — it auto-detects the Next.js project, configures the build, and gives you preview deployments for every PR. For small-to-medium projects, it's about as smooth as it gets in the frontend ecosystem today.

Future use

Certanly i will use for my own personal projects and even if some client wants some easy frontend expose to the public is good and quick way to make it happen.

 

omonteirox
Explorer

 

omonteirox_0-1787669865026.png

Week 4 done — deployed at https://business-card-1qdup01ww-omonteiroxs-projects.vercel.app/
 Ease of use: create-next-app to a running app took under a minute, and connecting the GitHub repo to Vercel was three clicks. The part that impressed me was that pushing to master redeploys with no pipeline to configure.
 Comparison: I mostly work on the SAP side — Fiori Elements and RAP — where the UI is generated from CDS annotations and the deploy goes through the ABAP transport chain. Next.js on Vercel is the opposite trade: nothing is generated for you, but there is also nothing between a commit and a live URL. Different tools for different problems; the Vercel loop is much tighter for a frontend that is genuinely custom.
Future use: yes for anything customer-facing sitting in front of SAP APIs. For apps inside the SAP landscape I would still reach for Fiori, since the launchpad, roles and catalogs come for free there.

 

kenzi
Explorer

vercel 20260825 message.png

August Joule Challenge Week 4

Name: Kenzi Sibuma
SAP Community ID: Kenzi

Vercel Project: https://vercel.com/kenzi5/business-card-app/KNyMGKXo3xmuXyFErfg1uQMtHjd5
Deployed App: https://business-card-app-kenzi5.vercel.app/

  • Ease of use: Very smooth overall. create-next-app made the setup quick, and Vercel looks much simpler than the MTA build and deployment process I am used to with SAP BTP.

  • Pain points: Most of my issues were actually local setup issues rather than Next.js itself. PowerShell initially blocked npx, and I also had to sort out my Git installation and configuration before I could commit and push the project. Once those were resolved, the framework itself was quite straightforward.

  • Comparison: I mainly work with SAP ABAP, SAPUI5/Fiori, CAP, BTP, and SAP integrations. Compared with those enterprise deployment processes, Next.js + Vercel feels much more lightweight and agile. However, UI5/BTP still has clear advantages for SAP enterprise applications because of Fiori standards, authentication, destinations, governance, OData, and deep S/4HANA integration.

  • Future use: Definitely. I can see myself using Next.js + Vercel for prototypes, customer-facing applications, AI/agent UIs, and standalone web applications. What I am most interested in now is how this fits with Joule Studio and SAP's agent-building direction — whether Next.js/Vercel becomes a recommended way of providing custom UIs for agents while SAPUI5 remains the preferred option for core transactional applications.

Overall, this was a very interesting Week 4 challenge for me because it introduced a development and deployment experience quite different from the traditional SAP stack. I am looking forward to exploring further how Next.js, Vercel, and possibly v0 can work together with SAP BTP, CAP, S/4HANA, and Joule Studio. - Kenzi Sibuma

rsraj
Explorer

Hello @shrinivasan_neelamegam 

rsraj_2-1787671036928.png

Ease of use: Looks great and easy to work with it.
Future use: Definitely would like to try in the near future; and eager to see the integration in the Joule Studio.

MatLakaemper
Participant

My Submission

MatLakaemper_0-1787674132167.png
very interesting challenge.

 

 

 

SyambabuAllu
Contributor

here is my submission 

SyambabuAllu_0-1787678222065.png

 

Ihor_Haranichev
Participant

Done! It was challenging!

Ihor_Haranichev_0-1787682199476.png

https://vercel.com/new/ih16/success?auto-redirect=true&developer-id=&external-id=&redirect-url=&bran...

Ease of use: Deploying from GitHub to Vercel took just a couple of clicks — framework and build settings were auto-detected, and Server Actions worked out of the box.

Future use: Fast deploys and native Server Action support make it a good fit for quick prototypes and demos that call external APIs like SAP CAP.

Secco
Active Participant

Secco_0-1787684162234.png

  • Ease of use: Really easy, and using AI to do it will make it a lot faster 
  • Pain points: No pain points 🙂
  • Comparison: It was my first experience
  • Future use: Sure, I'll just verify the costs first, you know ....
johnsonjos16
Participant

Screenshot 2026-08-25 155530.png
Ease of Use: This demo use case is very easy. But really need to see the SAP use case where this is needed instead of UI5. If this is for non SAP scenarios then, we need to compare with other tools/ platforms as well as this needs to know React.
Future use: Totally depends on the cost, when multiple environments are involced 

Labels in this area