3 ms·
>You have to have a product that works. it was completely outside the scope of my product. we have a mobile webapp that doesn't work in a uiwebview (ios). simp
by mlevental 9y ago
>You have to have a product that works.
it was completely outside the scope of my product. we have a mobile webapp that doesn't work in a uiwebview (ios). simple solution: pop out safari from a button. catastrophic failure: conference apps insist on keeping users in app and so those buttons load up the site in a uiwebview. in fact at the last moment (one day before the conference) i figured out a pretty viable solution, slapped it together in 6 hours, made calls to make appropriate changes on site (at the conference), and it should've gone okay.
>quantifiable value
this is what i think we're missing
- numbsafari 9y agoIt’s totally inside the scope of your product to work. You sold someone on your expertise and ability, but hadn’t done enough homework to know that your web app wouldn’t work in one of the most important ways their customers would interact with it? There’s a lot to learn here, but step one is owning up to your own mistakes and not blaming others.
- mlevental 9y agoI did know and it was exactly why I warned that customer that a uiwebview wouldn't work and that they needed a button. what I didn't know (because I was not privy to their conversations with their other app provider) was that that button could only open a uiwebview.