Bentley Developer Portal

We are pleased to announce the launch of the Bentley Developer portal!

A gateway for all third-party developers’ to access the robust Bentley programming technologies for customizing their own solutions that seamlessly integrate with and extend Bentley product capabilities.

Parents
  • HI Tamanud,

    thanks for the info.

    First feedback

    • [Impression] Overall, with accepting it's the first version, not bad (and much much much better than some pages designed by UX idiots like new Bentley "calendar", based on extensive tiling and grid organization, with tens of seconds to be loaded).
    • [Question] Why "join" is displayed when I am already logged in and I am already member of BDN?
    • [Wish] Please do not use "Analytical and modeling" etc. classification as primary on the main page. They are marketing bullshits, used by not engineers, thinking it sounds cool. Not at all.
      I am very sure that when somebody will visit the portal, there will be (nearly) always existing requirement defined by target product. In other words: "I am looking for information how to write code for MicroStation or OpenRoads Designer (because we use them in our company)".
      When products represent too detail split (and too many items to be displayed), use normally used terminology: building, civil, geo(spatial). Some from them are used already: Hydraulics and hydrology, Reality modeling...

    With regards,

      Jan

Reply
  • HI Tamanud,

    thanks for the info.

    First feedback

    • [Impression] Overall, with accepting it's the first version, not bad (and much much much better than some pages designed by UX idiots like new Bentley "calendar", based on extensive tiling and grid organization, with tens of seconds to be loaded).
    • [Question] Why "join" is displayed when I am already logged in and I am already member of BDN?
    • [Wish] Please do not use "Analytical and modeling" etc. classification as primary on the main page. They are marketing bullshits, used by not engineers, thinking it sounds cool. Not at all.
      I am very sure that when somebody will visit the portal, there will be (nearly) always existing requirement defined by target product. In other words: "I am looking for information how to write code for MicroStation or OpenRoads Designer (because we use them in our company)".
      When products represent too detail split (and too many items to be displayed), use normally used terminology: building, civil, geo(spatial). Some from them are used already: Hydraulics and hydrology, Reality modeling...

    With regards,

      Jan

Children