Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@heyheni - True. I did my best to explain how production-quality code differs a from the prototype-quality one, also reminded them that there are some screens in that prototype that were entirely based on images (which they agreed on for the first version of the prototype) . Implementing them alone may eat some 2 weeks off their scheduled time. I guess it's the classic case of an over-promising management (I am a subcontractor in that case), but it still grinds my gears.
-
you did even code it?
wouldn't it more efficient if you would use something like InVision to link your screens together and make it clickable?
https://www.invisionapp.com/craft -
@heyheni - Yes, I coded all of it - having to support multiple iPhone form factors was the main reason for going with a native implementation. Also there are some tricky transitions and collection view layout animations. To be honest, I liked the project a lot - the design is fantastic, the concepts are great, but oh, the management... Sadly, nothing in this world is perfect.
Client: "Let's code a prototype to show our intents to the customer. We have 96 screens to implement as a native app in 6 weeks"
~Prototype delivered in 6 weeks, despite some changes in the design on-the-go. Few months later~
Client: "The customer likes the prototype a lot. They would like to see some changes (another set of > 40 screens). It's still a prototype and the changes should be implemented in a month, but this time it has to use real data from external apis. We don't know which APIs yet, but it should also go live on the app store"
Like, seriously?
undefined