My take on New Apps VS ERPNext

Frappe Framework
,
1

After watching the debate (New App VS ERPNext) on Frappeverse day 2. It got me thinking and here is my take on it.

Split the company into two one is Frappe (a technology company) and second is Software solutions developer (ERPNext).

After the the split both should heavily invest heavily into each of their respective fields.

It would be great to know what are the views of rest of the community members.

2 Likes
2

To be honest I’m not fond of the new “Apps” structure present in v16.

Should be something optional.

I see Frappe and Erpnext as a centralization of potential. Where apps are visually interconnected.

The separation of Apps akin to Odoo doesn’t appeal to me.

6 Likes
3

Hi,

I’d like to discuss the development and integration of new apps within our ERPNext ecosystem. While I’m not opposed to new apps, I believe there are two distinct approaches we should consider:

Standalone Apps:

  • Apps like Drive and Mail can function independently, offering standalone services.
  • Integration with ERPNext can be optional, providing users with flexibility.

ERPNext-Dependent Apps:

  • Apps like CRM, Helpdesk, and Gameplan should extend the functionality of ERPNext.
  • If a user primarily needs CRM, they should be able to install both CRM and ERPNext, without requiring other ERPNext modules.
  • This approach aligns with the model we’ve successfully implemented with Frappe HR.

Key Considerations:

  • User Experience: Ensure that the integration between ERPNext and dependent apps is seamless, providing a cohesive user experience.
  • Modularity: Maintain modularity within ERPNext to allow users to install only the necessary modules, avoiding unnecessary overhead.
  • Scalability: Design apps to be scalable and adaptable to future needs, accommodating potential growth and changes.

By following these guidelines, we can create a robust and flexible ERPNext ecosystem that meets the diverse needs of our users.

5 Likes
4

I agree, with quality over quantity. There are many other open-source projects that can be integrated with ERPNext as well. For example, NextCloud for storage, etc. Expanding the ecosystem with thoughtful integrations while maintaining modularity will help ensure users have both flexibility and a seamless experience.

5

We have been using Nextcloud along with ERPNext for three years. Nextcloud offers Windows clients that sync files with the cloud to the local file system. This is a must for any knowledge worker working on Microsoft Office files locally. We made an integration one way from ERPnext to Nextcloud for our own use. We are open to contributing if a two-way integration is planned.

Yes, this will be a fantastic value addition to ERPNext

2 Likes
6

You’ll find lot of alternatives in Frappe apps.

For nextcloud alternative check GitHub - frappe/drive: An easy to use, document sharing and management solution.

1 Like
7

After watching the presentation I feel it is not about slicing current ERPNext into separate apps.

It is more about rebuilding it from scratch using the latest set of technologies and here Frappe Studio is going to play an important role. This rewriting will allow them (read Frappe/ERPNext) to get rid of legacy code and the complexities associated with it.

Having developed a few stand alone solutions in Frappe Framework I have always felt that there is very less freedom to style the input screens as per our requirements.

With the introduction of Frappe Studio I hope we will get free style UI screen building facility along with being able to use other matured and widely used UI/UX frameworks like Quasar Framework besides the standard Frappe UI.

I agree here that all those apps that can work as stand alone like CRM. Help Deks, etc. should be built in such a way that they can easily integrate with ERPNext with seamless two way data communication.

Anyone can easily integrate any number third party apps with ERPNext but building apps with similar features as found in third party apps (like NextCloud) in Frappe, actually helps Frappe push the envelop and also demonstrate to the world how flexible and powerful Frappe Framework is.

1 Like
8

This is huge video. What timestamp does New Apps vs ERPNext starts?
Thank you!

9

One rough hint would be the relevant day’s schedule on the Frappeverse 2024 site.

10

It’s at the very end of Day 2.

11

It starts here

1 Like
12

The idea of having portals for peripheral apps is great. This is what major ERP companies do. For example SAP has

  • Success Factors(SFSF) for SAP HCM
  • Cloud For Customer for SAP CRM
  • Ariba for SAP SRM

The main reason why such apps came into existence is to improve the user experience with modern and minimal design concepts. Mostly these apps can be used on the go.

I think all the peripherals of ERPNext needs a separate app. In that context the new apps like CRM, HRMS, Helpdesk … are driving in right direction.

The gap I see is the integration. Frappe should first focus on having a separate and solid middleware with all predefined integrations.

Now for me if I use ERPNext, I will be skeptical to adapt the new CRM, since except for the new UI, from a functional stand point the new CRM is still on the lower end. What will be CRM without Items. What will I Sell?.

We still need Items, Prices and other essential nuts and bolts of ERPNext for a complete CRM. Similarly Frappe HRMS.

We are extending the new CRM to a CPQ solution leveraging ERPNext. Have a look at our repo

open for Ideas

13

I think it will eventually boil down to how the modules/apps are coupled and exposed to each other.
There are certain parts of the applications that are completely optional and parts of processes that are completely working within their own silos.
Evbery change brings resistance, so expect some :slight_smile: